[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y/Uk/CnJq+F2idie@kroah.com>
Date: Tue, 21 Feb 2023 21:09:32 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Borislav Petkov <bp@...en8.de>
Cc: KP Singh <kpsingh@...nel.org>, linux-kernel@...r.kernel.org,
pjt@...gle.com, evn@...gle.com, jpoimboe@...nel.org,
tglx@...utronix.de, x86@...nel.org, hpa@...or.com,
peterz@...radead.org, pawan.kumar.gupta@...ux.intel.com,
kim.phillips@....com, alexandre.chartre@...cle.com,
daniel.sneddon@...ux.intel.com, corbet@....net, bp@...e.de,
linyujun809@...wei.com, jmattson@...gle.com,
José Oliveira <joseloliveira11@...il.com>,
Rodrigo Branco <rodrigo@...nelhacking.com>,
Alexandra Sandulescu <aesa@...gle.com>, stable@...r.kernel.org
Subject: Re: [PATCH v2 1/2] x86/speculation: Allow enabling STIBP with legacy
IBRS
On Tue, Feb 21, 2023 at 08:57:26PM +0100, Borislav Petkov wrote:
> On Tue, Feb 21, 2023 at 08:47:38PM +0100, Greg KH wrote:
> > Why does anyone need to "drop stable" from a patch discussion? That's
> > not a problem, we _WANT_ to see the patch review and discussion also
> > copied there to be aware of what is coming down the pipeline. So
> > whomever said that is not correct, sorry.
>
> Someone dropped stable because you used to send automated formletter
> mails that this is not how one should submit a patch to stable. I guess
> that is not needed anymore so I'll stop dropping stable.
I still send them, and so does 0-day, IF you send the emails
incorrectly. So far, that's not been the case for this series at all
(hint, there needs to be a cc: stable in the signed-off-by area of the
patch, that's all.)
thanks,
greg k-h
Powered by blists - more mailing lists