From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/intel-microcode: security bump to version 20210216
Date: Wed, 19 May 2021 21:56:56 +0200 [thread overview]
Message-ID: <877djubipj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87eee5nrak.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Mon, 17 May 2021 20:33:55 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Hi,
>>> +++ b/package/intel-microcode/intel-microcode.hash
>>> @@ -1,3 +1,3 @@
>>> # Locally computed
>>> -sha256 e42a264b7b86e80d013d6d00062467352c1f37e0aaea10fe5b51e4d8687921ab intel-microcode-20201118.tar.gz
>>> -sha256 d9e989e1a7747f3ce93cb749aceca67a430d36c9bebc6e3205e0b3af3ca6304b license
>>> +sha256 b855c81f78705f35341248a0603aa1a6e199ca7f59cd425e061b579329aa9eaa intel-microcode-20210216.tar.gz
>>> +sha256 03efb1491c7e899feb2665fa299363e64035e5444c1b8bc1f6ebed30de964e12 license
>> We like to have a quick explanation about why the hash of a license file
>> changes. In this case, I've explained that's because the year changed.
> Ups, indeed - Forgot to add that.
>> Applied to master, thanks.
> Thanks!
Committed to 2021.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2021-05-19 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 17:38 [Buildroot] [PATCH] package/intel-microcode: security bump to version 20210216 Peter Korsgaard
2021-05-17 17:51 ` Yann E. MORIN
2021-05-17 18:33 ` Peter Korsgaard
2021-05-19 19:56 ` 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=877djubipj.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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