public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: Josef Bacik <josef@toxicpanda.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	 linux-man@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	 Jeff Layton <jlayton@kernel.org>
Subject: [PATCH manpages] listmount.2: fix verbiage about continuing the iteration
Date: Wed, 13 Nov 2024 09:49:02 -0500	[thread overview]
Message-ID: <20241113-main-v1-1-a6b738d56e55@kernel.org> (raw)

The "+1" is wrong, since the kernel already increments the last_id. Fix
the manpage verbiage.

Cc: Josef Bacik <josef@toxicpanda.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
 man/man2/listmount.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man/man2/listmount.2 b/man/man2/listmount.2
index 717581b85e12dc172b7c478b4608665e9da74933..00ac6a60c0cfead5c462fcac44e61647d841ffe5 100644
--- a/man/man2/listmount.2
+++ b/man/man2/listmount.2
@@ -67,7 +67,7 @@ is used to tell the kernel what mount ID to start the list from.
 This is useful if multiple calls to
 .BR listmount (2)
 are required.
-This can be set to the last mount ID returned + 1 in order to
+This can be set to the last mount ID returned in order to
 resume from a previous spot in the list.
 .SH RETURN VALUE
 On success, the number of entries filled into

---
base-commit: df69651a5c1abb61bd0d7ba0791f65f427923f75
change-id: 20241113-main-192abec3348e

Best regards,
-- 
Jeff Layton <jlayton@kernel.org>


             reply	other threads:[~2024-11-13 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13 14:49 Jeff Layton [this message]
2024-11-13 15:59 ` [PATCH manpages] listmount.2: fix verbiage about continuing the iteration Alejandro Colomar
2024-11-13 17:12   ` Jeff Layton
2024-11-17  1:00     ` Alejandro Colomar

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=20241113-main-v1-1-a6b738d56e55@kernel.org \
    --to=jlayton@kernel.org \
    --cc=alx@kernel.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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