[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wg5kiiJ+LUChmw73mmi-=uyQrAO-fBTG6yr2ON_UnAoPg@mail.gmail.com>
Date: Tue, 3 Oct 2023 14:43:44 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Uros Bizjak <ubizjak@...il.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, Andy Lutomirski <luto@...nel.org>,
Nadav Amit <namit@...are.com>, Brian Gerst <brgerst@...il.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
"H . Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>,
Josh Poimboeuf <jpoimboe@...hat.com>
Subject: Re: [RFC PATCH 0/4] x86/percpu: Use segment qualifiers
On Tue, 3 Oct 2023 at 12:43, Ingo Molnar <mingo@...nel.org> wrote:
>
> So we could do this: we let it live in -tip for a cycle, in a separate
> branch, and observe what happens - it gets picked up by -next on
> a daily basis and most x86 developers test it. It won't be merged by other
> branches in -tip, it won't be pulled by others or relied on. If it
> conflicts with other bits we rebase it cleanly, no questions asked.
Sounds like a plan,
Linus
Powered by blists - more mailing lists