All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
	X86 ML <x86@kernel.org>
Subject: Re: [PATCH 0/2] x86/microcode/amd: Do not overwrite specific patch levels
Date: Fri, 10 Jul 2015 12:11:51 +0200	[thread overview]
Message-ID: <20150710101151.GA7538@nazgul.tnic> (raw)
In-Reply-To: <20150709150341.GB23766@khazad-dum.debian.net>

On Thu, Jul 09, 2015 at 12:03:41PM -0300, Henrique de Moraes Holschuh wrote:
> Is there any way to notify the user that 'processor microcode updates
> are not available on this system except through a firmware update' ?

What for?

Those microcode patch levels are final and shouldn't be upgraded at all.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

  reply	other threads:[~2015-07-10 10:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 20:14 [PATCH 0/2] x86/microcode/amd: Do not overwrite specific patch levels Borislav Petkov
2015-07-01 20:14 ` [PATCH 1/2] x86/microcode/amd: Extract current patch level read to a function Borislav Petkov
2015-07-01 20:14 ` [PATCH 2/2] x86/microcode/amd: Do not overwrite final patch levels Borislav Petkov
2015-07-09 15:03 ` [PATCH 0/2] x86/microcode/amd: Do not overwrite specific " Henrique de Moraes Holschuh
2015-07-10 10:11   ` Borislav Petkov [this message]
2015-07-10 15:12     ` Henrique de Moraes Holschuh
2016-03-26 23:31 ` Henrique de Moraes Holschuh
2016-03-27  8:31   ` Borislav Petkov
2016-03-27 12:32     ` Henrique de Moraes Holschuh
2016-03-27 15:47       ` Borislav Petkov
2016-05-02 15:30         ` Borislav Petkov
2016-05-06 12:43           ` Henrique de Moraes Holschuh
2016-05-06 13:23             ` Borislav Petkov

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=20150710101151.GA7538@nazgul.tnic \
    --to=bp@alien8.de \
    --cc=Aravind.Gopalakrishnan@amd.com \
    --cc=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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.