From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Filippo Sironi <sironi@amazon.de>
Cc: bp@alien8.de, prarit@redhat.com, linux-kernel@vger.kernel.org,
linux-edac@vger.kernel.org, stable@vger.kernel.org
Subject: x86/microcode: Don't duplicate code to update ucode cpu info and cpu info
Date: Tue, 31 Jul 2018 17:41:40 +0200 [thread overview]
Message-ID: <20180731154140.GA15243@kroah.com> (raw)
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>
---
To unsubscribe from this list: send the line "unsubscribe linux-edac" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Filippo Sironi <sironi@amazon.de>
Cc: bp@alien8.de, prarit@redhat.com, linux-kernel@vger.kernel.org,
linux-edac@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 17:41:40 +0200 [thread overview]
Message-ID: <20180731154140.GA15243@kroah.com> (raw)
In-Reply-To: <1533050970-14385-1-git-send-email-sironi@amazon.de>
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>
next reply other threads:[~2018-07-31 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 15:41 Greg Kroah-Hartman [this message]
2018-07-31 15:41 ` [PATCH] x86/microcode: Don't duplicate code to update ucode cpu info and cpu info Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-07-31 17:50 Greg Kroah-Hartman
2018-07-31 17:50 ` [PATCH] " Greg KH
2018-07-31 16:23 Filippo Sironi
2018-07-31 16:23 ` [PATCH] " Sironi, Filippo
2018-07-31 15:29 Filippo Sironi
2018-07-31 15:29 ` [PATCH] " Filippo Sironi
2018-09-02 12:16 ` [tip:x86/urgent] x86/microcode: Update the new microcode revision unconditionally tip-bot for Filippo Sironi
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=20180731154140.GA15243@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.