From: Josh Boyer <jwboyer@kernel.org>
To: John.Allen@amd.com
Cc: Linux Firmware <linux-firmware@kernel.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
Suravee.Suthikulpanit@amd.com,
Sherry Hurwitz <sherry.hurwitz@amd.com>
Subject: Re: [PATCH] linux-firmware: Update AMD cpu microcode
Date: Fri, 14 Dec 2018 08:06:26 -0500 [thread overview]
Message-ID: <CA+5PVA7jALa3uZJuABiB4s_Z9kiqQxGpA7Td6bpmeMpP3+CdWg@mail.gmail.com> (raw)
In-Reply-To: <20181129183805.14808-1-john.allen@amd.com>
On Thu, Nov 29, 2018 at 6:13 PM Allen, John <John.Allen@amd.com> wrote:
>
> * Update AMD cpu microcode for processor family 17h
>
> Key Name = AMD Microcode Signing Key (for signing microcode container files only)
> Key ID = F328AE73
> Key Fingerprint = FC7C 6C50 5DAF CC14 7183 57CA E4BE 5339 F328 AE73
>
> Signed-off-by: John Allen <john.allen@amd.com>
> ---
> WHENCE | 2 +-
> amd-ucode/microcode_amd_fam17h.bin | Bin 3364 -> 6476 bytes
> amd-ucode/microcode_amd_fam17h.bin.asc | 21 +++++++++++++--------
> 3 files changed, 14 insertions(+), 9 deletions(-)
Applied and pushed out.
josh
next prev parent reply other threads:[~2018-12-14 13:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 18:39 [PATCH] linux-firmware: Update AMD cpu microcode Allen, John
2018-12-14 13:06 ` Josh Boyer [this message]
2019-10-21 12:54 Allen, John
2019-10-22 11:29 ` Josh Boyer
2019-12-18 14:27 John Allen
2019-12-18 14:38 ` Josh Boyer
2021-10-25 19:18 John Allen
2021-11-15 17:09 John Allen
2022-02-14 20:50 John Allen
2022-04-08 15:37 John Allen
2022-04-08 19:48 ` John Allen
2022-09-30 15:51 John Allen
2023-01-31 20:13 John Allen
2023-04-14 16:13 John Allen
2023-07-13 18:05 John Allen
2023-07-18 19:11 ` John Allen
2023-07-18 23:19 John Allen
2023-08-08 19:02 John Allen
2023-10-19 17:03 John Allen
2023-12-05 20:10 John Allen
2024-01-16 21:07 John Allen
2024-01-17 15:06 ` Josh Boyer
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=CA+5PVA7jALa3uZJuABiB4s_Z9kiqQxGpA7Td6bpmeMpP3+CdWg@mail.gmail.com \
--to=jwboyer@kernel.org \
--cc=John.Allen@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=linux-firmware@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sherry.hurwitz@amd.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;
as well as URLs for NNTP newsgroup(s).