linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Usama Arif <usamaarif642@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, david@redhat.com,
	lorenzo.stoakes@oracle.com, hannes@cmpxchg.org,
	baohua@kernel.org, shakeel.butt@linux.dev, ziy@nvidia.com,
	laoar.shao@gmail.com, baolin.wang@linux.alibaba.com,
	Liam.Howlett@oracle.com, linux-kernel@vger.kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCH] PR_*ET_THP_DISABLE.2const: document addition of PR_THP_DISABLE_EXCEPT_ADVISED
Date: Mon, 1 Sep 2025 18:01:58 +0100	[thread overview]
Message-ID: <ba4acf5d-1092-48f3-9c99-b644a0aa96fa@gmail.com> (raw)
In-Reply-To: <hbwmiqb2qjyf4bemcbg2nwil4oceukvevml4jrilm4q4souv6e@hmjk4ubgavg2>



On 01/09/2025 17:40, Alejandro Colomar wrote:
> Hi Usama,
> 
> On Mon, Sep 01, 2025 at 05:18:22PM +0100, Usama Arif wrote:
>> I am not sure what the right time is to send the mandoc changes.
>> The patches have been merged into mm-new for more than 2 weeks.
>> We can still review it and I can resend if needed after the kernel release if that
>> is a more appropriate time?
> 
> No, this is fine.  Let's refine the patches for now.
> 
> Once we're done, I guess we can either wait until they arrive at Linus's
> tree, or if you're very confident this will reach a release eventually,
> we can merge it now here, and eventually fix it if something small
> changes later.  I don't mind too much.  It's more up to you, and how
> much you expect this to change before the actual release of Linux.
> 

Thanks!

Yeah I wouldnt expect this to change at all before the release. The patches
were extensively discussed on the mailing list and were acked by the THP
maintainers and reviewers, so the possibility of the interface changing
is extremely low.
> 
> Have a lovely day!
> Alex
> 


  reply	other threads:[~2025-09-01 17:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 16:09 [PATCH] PR_*ET_THP_DISABLE.2const: document addition of PR_THP_DISABLE_EXCEPT_ADVISED Usama Arif
2025-09-01 16:18 ` Usama Arif
2025-09-01 16:38   ` David Hildenbrand
2025-09-01 16:40   ` Alejandro Colomar
2025-09-01 17:01     ` Usama Arif [this message]
2025-09-01 16:36 ` Alejandro Colomar
2025-09-01 16:58   ` Usama Arif
2025-09-02  8:19     ` Alejandro Colomar
  -- strict thread matches above, loose matches on Subject: below --
2025-09-05 13:25 Usama Arif
2025-09-05 13:26 ` Usama Arif

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=ba4acf5d-1092-48f3-9c99-b644a0aa96fa@gmail.com \
    --to=usamaarif642@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=alx@kernel.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@meta.com \
    --cc=laoar.shao@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=shakeel.butt@linux.dev \
    --cc=ziy@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).