[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9rMTNQ+hZPG1cbpP2zA6Cq3-f=gXXPF3=WYhQWicEYV4w@mail.gmail.com>
Date: Mon, 2 Jan 2023 16:59:08 +0100
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Borislav Petkov <bp@...en8.de>
Cc: tglx@...utronix.de, mingo@...hat.com, dave.hansen@...ux.intel.com,
x86@...nel.org, hpa@...or.com,
Ricardo Neri <ricardo.neri-calderon@...ux.intel.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] x86: lib: Separate instruction decoder MMIO type from
MMIO trace
On 1/2/23, Borislav Petkov <bp@...en8.de> wrote:
> On Mon, Jan 02, 2023 at 03:49:23PM +0100, Jason A. Donenfeld wrote:
>> Do you think you could queue up this patch for 6.2 as a fix? It has
>> basically no chance of breakage and does fix a real symbol clash.
>>
>> https://lore.kernel.org/lkml/20221214203454.337299-1-Jason@zx2c4.com/
>>
>> This doesn't fix any existing compile error that I'm aware of, but if
>> this makes it into 6.2, it would avoid me having to carry it in a series
>> I'm working on,...
>
> Our general rule for urgent fixes going through tip is that they should
> qualify
> to be CC:stable fixes. And this one isn't so I think you should hold on to
> it
> and submit it along with the whole series as it is usually done.
Rest of series is intended to go through random.git tree, so it'd be
useful to not have to carry this there -- less pain.
Jason
Powered by blists - more mailing lists