mirror of https://lore.kernel.org/lkml/
 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>, X86 ML <x86@kernel.org>
Subject: Re: [PATCH 0/2] x86/microcode/amd: Do not overwrite specific patch levels
Date: Fri, 6 May 2016 15:23:04 +0200	[thread overview]
Message-ID: <20160506132304.GJ24044@pd.tnic> (raw)
In-Reply-To: <1462538627.4062065.600029521.1009E14F@webmail.messagingengine.com>

On Fri, May 06, 2016 at 09:43:47AM -0300, Henrique de Moraes Holschuh wrote:
> Unfortunately, I don't have any AMD boxes on hand to runtime-test them,
> which would be the reason why I didn't try backporting these on my own
> :-(

Ok, no probs. I'll send them to stable.

-- 
Regards/Gruss,
    Boris.

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

      reply	other threads:[~2016-05-06 13:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 20:14 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
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 [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=20160506132304.GJ24044@pd.tnic \
    --to=bp@alien8.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome