From: Andrew Morton <akpm@linux-foundation•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix•de>,
Ingo Molnar <mingo@redhat•com>, "H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Rik van Riel <riel@surriel•com>,
Qi Zheng <zhengqi.arch@bytedance•com>
Subject: Re: linux-next: duplicate patch in the tip tree
Date: Wed, 26 Feb 2025 20:40:48 -0800 [thread overview]
Message-ID: <20250226204048.9fd955ed7f965bf0df03adb6@linux-foundation.org> (raw)
In-Reply-To: <20250227144817.50618ab7@canb.auug.org.au>
On Thu, 27 Feb 2025 14:48:17 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi all,
>
> On Thu, 27 Feb 2025 14:44:10 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > The following commit is also in the mm tree as a different commit (but
> > the same patch):
> >
> > a37259732a7d ("x86/mm: Make MMU_GATHER_RCU_TABLE_FREE unconditional")
> >
> > This is commit
> >
> > a30104ede395 ("x86/mm: make MMU_GATHER_RCU_TABLE_FREE unconditional")
> >
> > in the mm-unstable branch of the mm tree.
> >
> > This is already causing a conflct in arch/x86/kernel/paravirt.c due commit
> >
> > f2c5c2105827 ("x86/mm: Remove pv_ops.mmu.tlb_remove_table call")
> >
> > in the tip tree (where I just used the tip tree version).
yes, I duplicated that match in mm.git so it can carry the series
"remove tlb_remove_page_ptdesc()".
> And another in arch/x86/mm/pgtable.c due to commit
>
> 530c12f84d2c ("x86: pgtable: convert to use tlb_remove_ptdesc()")
>
> in the tip tree (where I again just used the tip tree version).
Really, I'd mildly prefer that subsystem maintainers not cherrypick
patches from the middle of a series. An acked-by would be preferred.
I can understand the desire to test a patch within the subsystem's
tree, but that can (should?) be done by testing linux-next overall.
Whatever. I'll retain "x86: pgtable: convert to use
tlb_remove_ptdesc()" and shall figure it out within the merge window.
next prev parent reply other threads:[~2025-02-27 4:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 3:44 linux-next: duplicate patch in the tip tree Stephen Rothwell
2025-02-27 3:48 ` Stephen Rothwell
2025-02-27 4:40 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-12 3:09 Stephen Rothwell
2025-09-16 8:37 ` Lee Jones
2025-07-08 6:00 Stephen Rothwell
2025-07-08 6:48 ` Andrew Morton
2025-07-09 9:17 ` Borislav Petkov
2025-07-09 19:12 ` Andrew Morton
2025-07-09 19:43 ` Borislav Petkov
2025-05-12 5:04 Stephen Rothwell
2025-05-07 3:22 Stephen Rothwell
2025-05-07 7:55 ` Thomas Gleixner
2025-05-07 17:44 ` Ingo Molnar
2025-04-16 3:21 Stephen Rothwell
2025-04-16 14:38 ` Gregory CLEMENT
2025-01-15 5:33 Stephen Rothwell
2024-10-29 2:34 Stephen Rothwell
2024-10-29 4:30 ` Andrew Morton
2024-10-29 6:05 ` Stephen Rothwell
2024-10-29 7:52 ` Thomas Gleixner
2024-10-29 11:08 ` Peter Zijlstra
2024-09-11 5:24 Stephen Rothwell
2024-03-11 21:28 Stephen Rothwell
2023-10-04 2:33 Stephen Rothwell
2023-10-04 13:32 ` Jonathan Corbet
2023-10-04 15:41 ` Ingo Molnar
2023-06-02 3:04 Stephen Rothwell
2023-06-02 17:05 ` Andrew Morton
2023-01-13 1:40 Stephen Rothwell
2023-01-13 16:27 ` Jonathan Corbet
2023-01-13 21:51 ` Stephen Rothwell
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=20250226204048.9fd955ed7f965bf0df03adb6@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@redhat$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=riel@surriel$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
--cc=zhengqi.arch@bytedance$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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