From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 217253] mbind, set_mempolicy, migrate_pages: maxnode description is off-by-one
Date: Fri, 19 May 2023 11:46:24 +0000 [thread overview]
Message-ID: <bug-217253-11311-Xs2W46PuNN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217253-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217253
--- Comment #1 from Alejandro Colomar (alx@kernel.org) ---
Thanks for the investigation. I CCed the maintainer. If you have any
specific suggestions for fixing the documentation, would you mind
preparing a patch according to the ./CONTRIBUTING file in the
man-pages repository?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-05-19 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 14:05 [Bug 217253] New: mbind, set_mempolicy, migrate_pages: maxnode description is off-by-one bugzilla-daemon
2023-05-19 11:46 ` bugzilla-daemon [this message]
2023-05-19 11:51 ` [Bug 217253] " bugzilla-daemon
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=bug-217253-11311-Xs2W46PuNN@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@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