linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Jonathan Corbet <corbet@lwn.net>, Vinod Koul <vkoul@kernel.org>,
	Eric Biggers <ebiggers@kernel.org>,
	"Theodore Y. Ts'o" <tytso@mit.edu>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	Jonathan Cameron <jic23@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Jarkko Sakkinen <jarkko@kernel.org>,
	Mimi Zohar <zohar@linux.ibm.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Richard Weinberger <richard@nod.at>,
	Anton Ivanov <anton.ivanov@cambridgegreys.com>,
	Johannes Berg <johannes@sipsolutions.net>, <kernel@collabora.com>,
	<linux-mm@kvack.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <dmaengine@vger.kernel.org>,
	<linux-fscrypt@vger.kernel.org>, <linux-iio@vger.kernel.org>,
	<netdev@vger.kernel.org>, <workflows@vger.kernel.org>,
	<linux-integrity@vger.kernel.org>, <keyrings@vger.kernel.org>,
	<linux-sound@vger.kernel.org>, <linux-media@vger.kernel.org>,
	<linux-um@lists.infradead.org>
Subject: Re: [PATCH] docs: Remove literal markup from Documentation/ paths
Date: Fri, 4 Apr 2025 18:20:06 +0100	[thread overview]
Message-ID: <20250404182006.000038cc@huawei.com> (raw)
In-Reply-To: <20250404-doc-paths-unliteral-v1-1-74718785444e@collabora.com>

On Fri, 04 Apr 2025 11:37:28 -0400
Nícolas F. R. A. Prado <nfraprado@collabora.com> wrote:

> Given that the automarkup Sphinx plugin cross-references
> "Documentation/*.rst" strings in the text to the corresponding
> documents, surrounding those strings with the literal markup (``) not
> only adds unnecessary markup in the source files, but actually prevents
> the automatic cross-referencing to happen (as it doesn't happen in
> literal blocks).
> 
> Remove all the occurrences of the literal markup in
> "Documentation/*.rst" paths, except when the actual source file is being
> referred. Also change the surrounding text when needed so it reads well
> both in the source and the web page (eg. 'see file Doc...' -> 'see
> Doc...').
> 
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> ---
>  Documentation/admin-guide/mm/numa_memory_policy.rst       | 2 +-
>  Documentation/admin-guide/serial-console.rst              | 2 +-
>  Documentation/driver-api/dmaengine/client.rst             | 2 +-
>  Documentation/driver-api/nvdimm/security.rst              | 2 +-
>  Documentation/filesystems/fscrypt.rst                     | 4 ++--
>  Documentation/iio/adis16475.rst                           | 4 ++--
>  Documentation/iio/adis16480.rst                           | 4 ++--
>  Documentation/iio/adis16550.rst                           | 4 ++--
>  Documentation/iio/adxl380.rst                             | 4 ++--

Split patch up by subsystem would be a good thing here as we may
get other changes to these docs during the cycle and resulting
merge conflicts if this all goes in as one patch.


>  Documentation/kernel-hacking/hacking.rst                  | 6 +++---
>  Documentation/kernel-hacking/locking.rst                  | 2 +-
>  Documentation/networking/dsa/b53.rst                      | 2 +-
>  Documentation/networking/dsa/bcm_sf2.rst                  | 2 +-
>  Documentation/networking/dsa/dsa.rst                      | 2 +-
>  Documentation/networking/dsa/lan9303.rst                  | 2 +-
>  Documentation/networking/phy-link-topology.rst            | 2 +-
>  Documentation/process/adding-syscalls.rst                 | 2 +-
>  Documentation/process/submit-checklist.rst                | 7 ++++---
>  Documentation/security/keys/trusted-encrypted.rst         | 4 ++--
>  Documentation/sound/kernel-api/writing-an-alsa-driver.rst | 2 +-
>  Documentation/userspace-api/media/v4l/dev-sliced-vbi.rst  | 2 +-
>  Documentation/userspace-api/media/v4l/diff-v4l.rst        | 2 +-
>  Documentation/userspace-api/media/v4l/ext-ctrls-codec.rst | 4 ++--
>  Documentation/virt/uml/user_mode_linux_howto_v2.rst       | 2 +-
>  24 files changed, 36 insertions(+), 35 deletions(-)


  reply	other threads:[~2025-04-04 18:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 15:37 [PATCH] docs: Remove literal markup from Documentation/ paths Nícolas F. R. A. Prado
2025-04-04 17:20 ` Jonathan Cameron [this message]
2025-04-04 17:42   ` Jonathan Corbet
2025-04-05 15:31     ` Jonathan Cameron
2025-04-04 17:43 ` SeongJae Park
2025-04-05  1:17 ` Akira Yokosawa
2025-04-07 14:03   ` Nícolas F. R. A. Prado
2025-04-07  3:08 ` Mauro Carvalho Chehab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250404182006.000038cc@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dmaengine@vger.kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=jarkko@kernel.org \
    --cc=jic23@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=kernel@collabora.com \
    --cc=keyrings@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mchehab@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nfraprado@collabora.com \
    --cc=pabeni@redhat.com \
    --cc=perex@perex.cz \
    --cc=richard@nod.at \
    --cc=tiwai@suse.com \
    --cc=tytso@mit.edu \
    --cc=vkoul@kernel.org \
    --cc=workflows@vger.kernel.org \
    --cc=zohar@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).