linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] Documentation: convert path-lookup from markdown to resturctured text
Date: Mon, 10 Dec 2018 09:58:37 +1100	[thread overview]
Message-ID: <87h8fmcnoi.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20181206100912.535b351d@lwn.net>

[-- Attachment #1: Type: text/plain, Size: 2713 bytes --]

On Thu, Dec 06 2018, Jonathan Corbet wrote:

> On Thu, 06 Dec 2018 08:00:58 +1100
> NeilBrown <neilb@suse.com> wrote:
>
>> > Is there a reason you used "include" rather than just adding it to the
>> > TOC tree with the rest?  
>> 
>> Simple.  I didn't know what I was doing, and so randomly made changes until
>> the result seemed acceptable - then I stopped.  If there is a better
>> way, feel free to tweak that when applying.
>
> OK, tweaked and applied, thanks.
>
> jon

Thanks...

However we now have a stub section "Pathname lookup" which serves only
to introduce another stub sectoin "Pathname lookup in Linux", which does
little more than introduce the rest of the section.
This seems inelegant, and is probably why I went for the "include"
approach.

What would you think of something more like the following?

Thanks,
NeilBrown


diff --git a/Documentation/filesystems/index.rst b/Documentation/filesystems/index.rst
index ba921bdd5b06..605befab300b 100644
--- a/Documentation/filesystems/index.rst
+++ b/Documentation/filesystems/index.rst
@@ -363,8 +363,18 @@ encryption of files and directories.
 Pathname lookup
 ===============
 
-Pathname lookup in Linux is a complex beast; the document linked below
-provides a comprehensive summary for those looking for the details.
+
+This write-up is based on three articles published at lwn.net:
+
+- <https://lwn.net/Articles/649115/> Pathname lookup in Linux
+- <https://lwn.net/Articles/649729/> RCU-walk: faster pathname lookup in Linux
+- <https://lwn.net/Articles/650786/> A walk among the symlinks
+
+Written by Neil Brown with help from Al Viro and Jon Corbet.
+It has subsequently been updated to reflect changes in the kernel
+including:
+
+- per-directory parallel name lookup.
 
 .. toctree::
    :maxdepth: 2
diff --git a/Documentation/filesystems/path-lookup.rst b/Documentation/filesystems/path-lookup.rst
index 30a155736afe..9d6b68853f5b 100644
--- a/Documentation/filesystems/path-lookup.rst
+++ b/Documentation/filesystems/path-lookup.rst
@@ -1,18 +1,3 @@
-========================
-Pathname lookup in Linux
-========================
-
-This write-up is based on three articles published at lwn.net:
-
-- <https://lwn.net/Articles/649115/> Pathname lookup in Linux
-- <https://lwn.net/Articles/649729/> RCU-walk: faster pathname lookup in Linux
-- <https://lwn.net/Articles/650786/> A walk among the symlinks
-
-Written by Neil Brown with help from Al Viro and Jon Corbet.
-It has subsequently been updated to reflect changes in the kernel
-including:
-
-- per-directory parallel name lookup.
 
 Introduction to pathname lookup
 ===============================

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-12-09 22:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19  0:55 [PATCH] Documentation: update path-lookup.md for parallel lookups NeilBrown
2018-11-20 16:38 ` Jonathan Corbet
2018-12-04 23:02 ` [PATCH 1/2] Documentation: convert path-lookup from markdown to resturctured text NeilBrown
2018-12-04 23:04   ` [PATCH 2/2] Documentation: path-lookup - update externel refs NeilBrown
2018-12-05 19:46   ` [PATCH 1/2] Documentation: convert path-lookup from markdown to resturctured text Jonathan Corbet
2018-12-05 21:00     ` NeilBrown
2018-12-06 17:09       ` Jonathan Corbet
2018-12-09 22:58         ` NeilBrown [this message]
2018-12-20 15:54           ` Jonathan Corbet
2018-12-21  0:33             ` NeilBrown

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=87h8fmcnoi.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).