From: Alejandro Colomar <alx@kernel.org>
To: Svetly Todorov <svetly.todorov@memverge.com>
Cc: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
Gregory Price <gregory.price@memverge.com>,
"Huang, Ying" <ying.huang@intel.com>
Subject: Re: [PATCH v4] man2: add MPOL_WEIGHTED_INTERLEAVE documentation
Date: Mon, 18 Mar 2024 16:09:28 +0100 [thread overview]
Message-ID: <ZfhZKLOVh9AOsWjr@debian> (raw)
In-Reply-To: <CE2DBC36-6297-4B9E-BA65-F14129A927EB@memverge.com>
[-- Attachment #1: Type: text/plain, Size: 2357 bytes --]
On Mon, Mar 18, 2024 at 02:38:48PM +0000, Svetly Todorov wrote:
> Happy Monday Alex,
Happy Monday Svetly!
> Thanks for looking at this over the weekend! Hopefully
> not too many more changes to go.
Nah, I think we're almost done. The patch LGTM.
> > We should document the kernel version that added this.
> > Please look for other (since ...) in the same page
> >
> > Have a lovely night!
> > Alex
>
> I was referencing MPOL_LOCAL in the same page and there are
> two commits listed under it:
>
> > .BR MPOL_LOCAL " (since Linux 3.8)”
> > .\" commit 479e2802d09f1e18a97262c4c6f8f17ae5884bd8
> > .\" commit f2a07f40dbc603c15f8b06e6ec7f768af67b424f
>
> I want to add a similar comment for MPOL_WEIGHTED_INTERLEAVE
> but I’m not sure what the equivalent would be.
> I’m thinking to have something like
>
> > .BR MPOL_WEIGHTED_INTERLEAVE " since (Linux 6.9)"
Yes, the above is fine.
> > .\" commit fa3bea4e1f8202d787709b7e3654eb0a99aed758
And yeah, this is good too.
> Where fa3bea... is the commit in the kernel git
> for the weighted interleave patch:
Yup. That commit is already in Linus's tree:
alx@debian:~/src/linux/linux/master$ git describe --contains fa3bea4e1f82
fatal: cannot describe 'fa3bea4e1f8202d787709b7e3654eb0a99aed758'
alx@debian:~/src/linux/linux/master$ git describe fa3bea4e1f82
v6.8-rc5-108-gfa3bea4e1f82
alx@debian:~/src/linux/linux/master$ git log --oneline torvalds/master | grep fa3bea4e1f82
fa3bea4e1f82 mm/mempolicy: introduce MPOL_WEIGHTED_INTERLEAVE for weighted interleaving
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/?h=mm-stable-2024-03-13-20-04&id=fa3bea4e1f8202d787709b7e3654eb0a99aed758
>
> (Forgive me, not sure if there’s a way to shorten long links like that).
No problem. I don't either. :)
> I can’t tell why there are two commits listed under MPOL_LOCAL, though.
Maybe one commit significantly changed the feature. Don't worry;
normally there's just 1 commit listed in the comments.
> Do you think just fa3ea... would be sufficient?
Yup! Please send and I'll apply already. (And remember to add the
'Reviewed-by: "Huang, Ying" <ying.huang@intel.com>'.)
Cheers,
Alex
>
> Svetly
>
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-18 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-16 19:50 [PATCH v4] man2: add MPOL_WEIGHTED_INTERLEAVE documentation Svetly Todorov
2024-03-16 21:06 ` Alejandro Colomar
2024-03-18 14:38 ` Svetly Todorov
2024-03-18 15:09 ` Alejandro Colomar [this message]
2024-03-19 10:05 ` Stefan Puiu
2024-03-19 11:33 ` 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=ZfhZKLOVh9AOsWjr@debian \
--to=alx@kernel.org \
--cc=gregory.price@memverge.com \
--cc=linux-man@vger.kernel.org \
--cc=svetly.todorov@memverge.com \
--cc=ying.huang@intel.com \
/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.