From: Borislav Petkov <bp@alien8.de>
To: "Raj, Ashok" <ashok.raj@intel.com>
Cc: Chen Yu <yu.c.chen@intel.com>,
Andy Lutomirski <luto@amacapital.net>,
"Hansen, Dave" <dave.hansen@intel.com>,
Len Brown <len.brown@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Tony Luck <tony.luck@intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][v2] x86/microcode/intel: check cpu stepping and processor flag before saving microcode
Date: Mon, 16 Nov 2020 22:46:22 +0100 [thread overview]
Message-ID: <20201116214622.GG1131@zn.tnic> (raw)
In-Reply-To: <20201116213019.GB76389@otc-nc-03>
On Mon, Nov 16, 2020 at 01:30:19PM -0800, Raj, Ashok wrote:
> Stable is still left below. with #v4.10+
>
> Do you want to keep this? Also do you want him to resend or you have that
> covered?
No Ashok, read the section
"For all other submissions, choose one of the following procedures"
here: Documentation/process/stable-kernel-rules.rst
> Seems clear to me, and the commit log cleanup also makes sense. I
> don't have a system myself,. Will wait for Chen Yu to confirm if it
> works for him as well.
Ok, I'll wait a bit before queuing it for urgent.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-11-16 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 1:59 [PATCH][v2] x86/microcode/intel: check cpu stepping and processor flag before saving microcode Chen Yu
2020-11-16 12:27 ` Borislav Petkov
2020-11-16 21:30 ` Raj, Ashok
2020-11-16 21:46 ` Borislav Petkov [this message]
2020-11-17 2:25 ` Chen Yu
2020-11-17 9:18 ` Borislav Petkov
2020-11-17 9:40 ` Chen Yu
2020-11-17 9:37 ` [tip: x86/urgent] x86/microcode/intel: Check patch signature before saving microcode for early loading tip-bot2 for Chen Yu
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=20201116214622.GG1131@zn.tnic \
--to=bp@alien8.de \
--cc=ashok.raj@intel.com \
--cc=dave.hansen@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yu.c.chen@intel.com \
/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