From: Greg KH <gregkh@linuxfoundation.org>
To: "Sironi, Filippo" <sironi@amazon.de>
Cc: Borislav Petkov <bp@alien8.de>,
"prarit@redhat.com" <prarit@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] x86/microcode: Don't duplicate code to update ucode cpu info and cpu info
Date: Tue, 31 Jul 2018 19:50:35 +0200 [thread overview]
Message-ID: <20180731175035.GB16667@kroah.com> (raw)
In-Reply-To: <5C646084-CE58-41A5-AC57-E42D996C4212@amazon.de>
On Tue, Jul 31, 2018 at 04:23:00PM +0000, Sironi, Filippo wrote:
>
> > On 31. Jul 2018, at 17:41, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Jul 31, 2018 at 05:29:30PM +0200, Filippo Sironi wrote:
> >> ... on late microcode loading when handling a CPU that's already been
> >> updated and a CPU that's yet to be updated.
> >>
> >> Signed-off-by: Filippo Sironi <sironi@amazon.de>
> >> ---
> >> arch/x86/kernel/cpu/microcode/amd.c | 15 +++++++++------
> >> arch/x86/kernel/cpu/microcode/intel.c | 10 ++++++----
> >> 2 files changed, 15 insertions(+), 10 deletions(-)
> >
> > <formletter>
> >
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree. Please read:
> > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> > for how to do this properly.
> >
> > </formletter>
>
> Greg,
>
> If you're concerned that this isn't a fix, keep in mind that this is going
> to be a prerequisite for https://lore.kernel.org/patchwork/patch/969070/ ,
> which is a bug and was sent to stable.
{sigh} No, go read the file please...
greg k-h
prev parent reply other threads:[~2018-07-31 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1533050970-14385-1-git-send-email-sironi@amazon.de>
2018-07-31 15:41 ` [PATCH] x86/microcode: Don't duplicate code to update ucode cpu info and cpu info Greg KH
[not found] ` <5C646084-CE58-41A5-AC57-E42D996C4212@amazon.de>
2018-07-31 17:50 ` Greg KH [this message]
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=20180731175035.GB16667@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=sironi@amazon.de \
--cc=stable@vger.kernel.org \
/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