All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, x86-ml <x86@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86/microcode for 6.7
Date: Sun, 12 Nov 2023 20:56:57 +0100	[thread overview]
Message-ID: <20231112195657.GCZVEuCVfBYuDVoLHG@fat_crate.local> (raw)
In-Reply-To: <CAHk-=wi_ko54kPH3Jc_eEXHrxjJOQ_TDkeo1cjU1pdeC+kzATg@mail.gmail.com>

On Sun, Nov 12, 2023 at 11:41:53AM -0800, Linus Torvalds wrote:
> I can verify that this makes my boot logs look sane again.

Cool.

> I'm not applying this directly, and will let you do the final version
> in the tip tree (split into two?), but thought I'd at least ack that
> it works for me.

Thanks!

So I was looking at the Intel side earlier and it doesn't dump the
revision it had *before* the early loading. And people have asked for
that functionality - to be able to dump the revision which got
overwritten.

So I'll try to pull up that code and use for both drivers, test on all
machines and send out a proper set.

And yap, you'll get that eventually through tip, in time for 6.7.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

      reply	other threads:[~2023-11-12 19:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 11:06 [GIT PULL] x86/microcode for 6.7 Borislav Petkov
2023-11-04 19:01 ` pr-tracker-bot
2023-11-11 22:19 ` Linus Torvalds
2023-11-11 22:35   ` Borislav Petkov
2023-11-12 12:23     ` Borislav Petkov
2023-11-12 19:41       ` Linus Torvalds
2023-11-12 19:56         ` 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=20231112195657.GCZVEuCVfBYuDVoLHG@fat_crate.local \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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.