From: Thomas Gleixner <tglx@linutronix.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>
Cc: 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>
Subject: Re: linux-next: duplicate patches in the tip tree
Date: Tue, 11 Mar 2025 13:56:02 +0100 [thread overview]
Message-ID: <878qpb20bh.ffs@tglx> (raw)
In-Reply-To: <20250311224338.4baf583c@canb.auug.org.au>
On Tue, Mar 11 2025 at 22:43, Stephen Rothwell wrote:
> On Tue, 11 Mar 2025 02:02:40 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>> There's presumably a better way of doing this, but it's really the
>> first time it has happened in N years so it isn't obviously worth
>> investing in setting something up.
>
> This is why we have shared stable branches. If the tip guys have all
> those commits in a branch that they guarantee will not rebase (or be
> rewritten), then you could fetch that branch and merge it into your
> tree somewhere.
tip timers/vdso is stable and won't be rebased. It might get delta fixes
on top, but that should be not a problem.
Andrew, feel free to pull that in.
Thanks,
tglx
next prev parent reply other threads:[~2025-03-11 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 4:08 linux-next: duplicate patches in the tip tree Stephen Rothwell
2025-03-11 9:02 ` Andrew Morton
2025-03-11 11:43 ` Stephen Rothwell
2025-03-11 12:56 ` Thomas Gleixner [this message]
2025-03-25 21:47 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-03-20 9:46 Stephen Rothwell
2025-03-20 11:13 ` Mark Brown
2024-12-09 2:29 Stephen Rothwell
2024-12-09 11:08 ` Peter Zijlstra
2024-12-09 19:45 ` Andrew Morton
2024-12-09 20:21 ` Suren Baghdasaryan
2024-12-09 22:53 ` Thomas Gleixner
2024-11-18 21:02 Stephen Rothwell
2024-03-03 22:21 Stephen Rothwell
2024-03-04 9:21 ` Ingo Molnar
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=878qpb20bh.ffs@tglx \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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