From: Baoquan He <bhe@redhat.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, chrisl@kernel.org, baohua@kernel.org
Subject: Re: [PATCH v2] iman/man2/swapon.2: update priority section
Date: Tue, 25 Nov 2025 10:25:49 +0800 [thread overview]
Message-ID: <aSUTrQFzmGwheWgz@MiWiFi-R3L-srv> (raw)
In-Reply-To: <wepvktnkiofwnp2xyifkr3mcs4gjdqafvvydyelv5wurmedrnv@zqn7e5g6ksmj>
On 11/24/25 at 05:56pm, Alejandro Colomar wrote:
> Hi Baoquan,
>
> On Fri, Oct 17, 2025 at 08:31:10PM +0800, Baoquan He wrote:
> > This update the description about default priority value which is
> > changed in kernel.
> >
> > Link: https://lore.kernel.org/all/20251011081624.224202-1-bhe@redhat.com/
> > Signed-off-by: Baoquan He <bhe@redhat.com>
> > Cc: chrisl@kernel.org
> > Cc: baohua@kernel.org
> > Cc: alx@kernel.org
> > ---
> > man/man2/swapon.2 | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/man/man2/swapon.2 b/man/man2/swapon.2
> > index df5e8d8c7ec6..20e213827733 100644
> > --- a/man/man2/swapon.2
> > +++ b/man/man2/swapon.2
> > @@ -60,9 +60,8 @@ These functions may be used only by a privileged process (one having the
> > capability).
> > .SS Priority
> > Each swap area has a priority, either high or low.
> > -The default priority is low.
> > -Within the low-priority areas,
> > -newer areas are even lower priority than older areas.
> > +The default priority is the lowest,
> > +and all default areas share the same priority value, -1.
>
> Please document the old behavior in the HISTORY section.
Sure, I will send a new version once the relevant kernel patches are
merged into linus's mainline kernel. Now, it's in Andrew Mortan's MM
tree, the commits are temporary.
Will add the old behaviour as you suggested in v3. Thanks a lot for your
suggestion.
Thanks
Baoquan
prev parent reply other threads:[~2025-11-25 2:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 12:31 [PATCH v2] iman/man2/swapon.2: update priority section Baoquan He
2025-10-20 9:21 ` Barry Song
2025-10-20 13:09 ` Baoquan He
2025-10-21 16:58 ` Alejandro Colomar
2025-11-24 16:56 ` Alejandro Colomar
2025-11-25 2:25 ` Baoquan He [this message]
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=aSUTrQFzmGwheWgz@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=alx@kernel.org \
--cc=baohua@kernel.org \
--cc=chrisl@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