From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Bernd Kuhls <bernd@kuhls.net>
Subject: Re: [Buildroot] [PATCH] package/intel-microcode: security bump to version 20231114
Date: Thu, 30 Nov 2023 09:00:43 +0100 [thread overview]
Message-ID: <8734wnacwk.fsf@48ers.dk> (raw)
In-Reply-To: <20231115112643.3093266-1-peter@korsgaard.com> (Peter Korsgaard's message of "Wed, 15 Nov 2023 12:26:42 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Includes fixes for INTEL-SA-00950:
> https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00950.html
> https://lock.cmpxchg8b.com/reptar.html
> https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20231114
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2023.02.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-11-30 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 11:26 [Buildroot] [PATCH] package/intel-microcode: security bump to version 20231114 Peter Korsgaard
2023-11-18 13:21 ` Yann E. MORIN
2023-11-30 8:00 ` Peter Korsgaard [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=8734wnacwk.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.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