Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp982694yba; Fri, 26 Apr 2019 12:00:32 -0700 (PDT) X-Google-Smtp-Source: APXvYqwxXPfysoWF4wzPtF14A6GXx2PU597rqTNrvciRC3ztSH85DDFjr73fNK5GruINgK2vdrXG X-Received: by 2002:a17:902:61:: with SMTP id 88mr47038219pla.166.1556305232614; Fri, 26 Apr 2019 12:00:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556305232; cv=none; d=google.com; s=arc-20160816; b=AVpVnBoqwsmwqNu8RS1XbXJO8O9sQSURRYgxHYDWlXix9sCcashLsSNq8PnD/Mr4lr k6Jh0J4q7kNyR7DFgLSRlGCaeWII2gb8S44Fp/MCAr24eS8e4e3bFK3IPdbv+gw0Rzo+ 8Om4zZjptNd/Is5YI+F0WcJ1bl362veNLBSA4KUK0J2nESzSVOZ7Fw6BkXPT9mjdVXUM aBera8ZfQmGnShbDb+dl+PaNjeW7zMECOuugn5bLC19tZUKAT43muV1N3VQGzT0CYYAg IQl0dMCwlr0dghgannoaNcBMmGfJ8ObaD6uze6vW/D0fWTPPHz9e+YToydyZD6PCGb3k D/WA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :organization:in-reply-to:subject:cc:to:from; bh=EMbTKRdjfA2XNFqkBQgUSqbGNO0LpVAa1XZ9WM7NSYU=; b=TsN6rm1gQnBPsxguXrcW/zE56wfa21sDykU33zMhOFg3SUETBHxPM8Kn9uzZn00Hpy MeMF0j87pvlBXBL2syGD/2H82xRKb/Nhszje0NhTwkPIKECfpMlgYrNifqGD46NujJih LrNpWbUsuzwNOVDsFgXOWrkMM1ryg/GlyoOLlmvWM+MMx5psh+ad4Xtq8dckZ4tEzF0b i6VmuGJQIvmfer4orQCbvFLh3TDakfhiwo/sGjdS1iNCDYpj9OXXuteDbNKA/7ZIv1Hx xorzsW6D+p2rVy7J18oRgSUrofXUHTsAyFECF1oALoUSzIlmrT7fo5LjHUF0OdyL9BWP WeuQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g123si27582139pfb.24.2019.04.26.12.00.17; Fri, 26 Apr 2019 12:00:32 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726569AbfDZS7C (ORCPT + 99 others); Fri, 26 Apr 2019 14:59:02 -0400 Received: from mga05.intel.com ([192.55.52.43]:5933 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726358AbfDZS7C (ORCPT ); Fri, 26 Apr 2019 14:59:02 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Apr 2019 11:59:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,398,1549958400"; d="scan'208";a="168268245" Received: from dlevy1-mobl1.ger.corp.intel.com (HELO localhost) ([10.252.47.21]) by fmsmga001.fm.intel.com with ESMTP; 26 Apr 2019 11:58:59 -0700 From: Jani Nikula To: Jonathan Corbet Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Matthew Wilcox , Mauro Carvalho Chehab Subject: Re: [PATCH 1/2] Docs: An initial automarkup extension for sphinx In-Reply-To: <20190426105209.1e414eae@lwn.net> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20190425200125.12302-1-corbet@lwn.net> <20190425200125.12302-2-corbet@lwn.net> <87tvelrv8d.fsf@intel.com> <20190426105209.1e414eae@lwn.net> Date: Fri, 26 Apr 2019 21:58:58 +0300 Message-ID: <87zhoch9u5.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 26 Apr 2019, Jonathan Corbet wrote: > I am not at all opposed to a more proper solution that might, in the > long term, produce more deterministic results. I can even try to work in > that direction. But this is something that can be done now that, IMO, > doesn't in any way close off a better implementation in the future. If we > agree that we should automatically generate references for occurrences of > "function()", we can change how that is actually done later. > > I'll look into this further, but my inclination is to go forward with what > I have now. It's simple and easy to understand, and doesn't seem to screw > up anywhere in the current body of kernel docs as far as I can tell. Fair enough. It's most important that this doesn't block us from switching to a different implementation later once someone figures it out. BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center