All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Tang <danielzgtg.opensource@gmail.com>
To: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Fox Chen <foxhlchen@gmail.com>
Cc: NeilBrown <neilb@suse.de>, Jonathan Corbet <corbet@lwn.net>,
	vegard.nossum@oracle.com, viro@zeniv.linux.org.uk,
	rdunlap@infradead.org, grandmaster@al2klimov.de
Subject: [PATCH v2] docs: path-lookup: fix unrenamed WALK_GET
Date: Tue, 03 Mar 2026 17:45:02 -0500	[thread overview]
Message-ID: <5332975.31r3eYUQgx@daniel-desktop3> (raw)
In-Reply-To: <13098721.O9o76ZdvQC@daniel-desktop3>

Fixes: de9414adafe4 ("docs: path-lookup: update WALK_GET, WALK_PUT desc")
Signed-off-by: Daniel Tang <danielzgtg.opensource@gmail.com>
---
 Documentation/filesystems/path-lookup.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/filesystems/path-lookup.rst b/Documentation/filesystems/path-lookup.rst
index 9ced1135608e..6957c70f18db 100644
--- a/Documentation/filesystems/path-lookup.rst
+++ b/Documentation/filesystems/path-lookup.rst
@@ -1364,7 +1364,7 @@ it sets ``LOOKUP_AUTOMOUNT``, as does "``quotactl()``" and the handling of
 symlinks.  Some system calls set or clear it implicitly, while
 others have API flags such as ``AT_SYMLINK_FOLLOW`` and
 ``UMOUNT_NOFOLLOW`` to control it.  Its effect is similar to
-``WALK_GET`` that we already met, but it is used in a different way.
+``WALK_TRAILING`` that we already met, but it is used in a different way.
 
 ``LOOKUP_DIRECTORY`` insists that the final component is a directory.
 Various callers set this and it is also set when the final component
-- 
2.51.0




  reply	other threads:[~2026-03-03 22:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-03 22:40 [PATCH] docs: path-lookup: fix unrenamed WALK_GET Daniel Tang
2026-03-03 22:45 ` Daniel Tang [this message]
2026-03-09 16:18   ` [PATCH v2] " Jonathan Corbet
2026-03-10  1:05     ` [PATCH v3] " Daniel Tang
2026-03-22 20:54       ` Jonathan Corbet

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=5332975.31r3eYUQgx@daniel-desktop3 \
    --to=danielzgtg.opensource@gmail.com \
    --cc=corbet@lwn.net \
    --cc=foxhlchen@gmail.com \
    --cc=grandmaster@al2klimov.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=rdunlap@infradead.org \
    --cc=vegard.nossum@oracle.com \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.