Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5395874ybi; Wed, 12 Jun 2019 01:40:06 -0700 (PDT) X-Google-Smtp-Source: APXvYqzW1GlaRaMUp29e2bb1ggE7aKcncI1oM0GalKxcku95HDoXBmvSI443/s4mEYfJ1ApiXNM3 X-Received: by 2002:a17:90a:6505:: with SMTP id i5mr12417210pjj.47.1560328806473; Wed, 12 Jun 2019 01:40:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560328806; cv=none; d=google.com; s=arc-20160816; b=rch0ZV2dWv16B2UNs2s6cO5p+lO3ozxnVp94Um1fx7k0nWkT1gtnl5xES1/ucXc7YK Ib1nw+/ZMRUyy2owUHmsRaxp7KvbyFUZ9eBuLY3EO4jIjRwCfP+YH82iVuDmcu8zPmWt 7exnzmofDJtubnouM2az82PbYy+p1B3Yl4gf4wUppiXybbPDgiN0cl0VzotFMGuAS0dx QXkOEg7w7GAEpZEVXU/HlOb56gSSkLt36UfpPkem3nGHeFHB8Dqp9U1zjvZJPgF4vwY/ E4tf0sCAH3Ca/Tag3iEGMVwqs0xmELxZAIq2HsP41aPVPhRoVFiFhwP//d5bSDLVNDFj 9XmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:references:organization:in-reply-to:subject:cc:to :from; bh=nLj4NrNP95IDBQv6a7GhwwSmXTZZoenW32q+2kYhTSo=; b=pZsgluQjRoH72YDfUE7DD/dNvTG5Mry8y+SBoqJqImLme1/HUtVYdA/w4za/WdDnMx /XkXSWQuSiSM4YP+/JeJHq3YHI7xhUdQ1GJT9u+krAxxkbVJ1r/6Qsy7G+YSQ8+px35O uRxrqwljZzfwvVmdggV4EdxKl1H+5BBX+z2w97aG63GxNVLzekDQ07QwqWau9UHI+1xB tPthCj5+7H8Y8BmLhNmpywD/ASb5k9CHpLTLa3Oq3gd2e1ECq1MkVSbdQRtRYYCiGNJ1 NwUUoMEGFRtUkDXyGKQKIIxMw1nUZ61mMSTCErFnVYbKbtDry7qa7POaixWvmtbtvwcK E0Eg== 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 k32si5061810pjb.11.2019.06.12.01.39.50; Wed, 12 Jun 2019 01:40:06 -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 S1726196AbfFLHyP convert rfc822-to-8bit (ORCPT + 99 others); Wed, 12 Jun 2019 03:54:15 -0400 Received: from mga17.intel.com ([192.55.52.151]:56056 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725810AbfFLHyP (ORCPT ); Wed, 12 Jun 2019 03:54:15 -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 fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jun 2019 00:54:14 -0700 X-ExtLoop1: 1 Received: from jnikula-mobl3.fi.intel.com (HELO localhost) ([10.237.66.150]) by fmsmga001.fm.intel.com with ESMTP; 12 Jun 2019 00:54:12 -0700 From: Jani Nikula To: =?utf-8?Q?Andr=C3=A9?= Almeida , linux-doc@vger.kernel.org Cc: linux-kernel@vger.kernel.org, corbet@lwn.net, kernel@collabora.com, =?utf-8?Q?Andr=C3=A9?= Almeida Subject: Re: [PATCH] sphinx.rst: Add note about code snippets embedded in the text In-Reply-To: <20190611200316.30054-1-andrealmeid@collabora.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20190611200316.30054-1-andrealmeid@collabora.com> Date: Wed, 12 Jun 2019 10:57:12 +0300 Message-ID: <87ftofxmlj.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 11 Jun 2019, André Almeida wrote: > There's a paragraph that explains how to create fixed width text block, > but it doesn't explains how to create fixed width text inline, although > this feature is really used through the documentation. Fix that adding a > quick note about it. I don't mind this addition, it's simple enough, but in general I think we should reference the Sphinx and reStructuredText documentation, whichever is more applicable, instead of duplicating the documentation. The idea is that this document describes how to use them in kernel. Contrast with coding style and language reference. BR, Jani. > > Signed-off-by: André Almeida > --- > Documentation/doc-guide/sphinx.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/doc-guide/sphinx.rst b/Documentation/doc-guide/sphinx.rst > index c039224b404e..f48abc07f4c5 100644 > --- a/Documentation/doc-guide/sphinx.rst > +++ b/Documentation/doc-guide/sphinx.rst > @@ -218,7 +218,7 @@ Here are some specific guidelines for the kernel documentation: > examples, etc.), use ``::`` for anything that doesn't really benefit > from syntax highlighting, especially short snippets. Use > ``.. code-block:: `` for longer code blocks that benefit > - from highlighting. > + from highlighting. For a short snippet of code embedded in the text, use \`\`. > > > the C domain -- Jani Nikula, Intel Open Source Graphics Center