Linux EFI development
 help / color / mirror / Atom feed
From: Tom Lendacky <thomas.lendacky@amd.com>
To: Ard Biesheuvel <ardb@kernel.org>, Borislav Petkov <bp@alien8.de>
Cc: linux-efi <linux-efi@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Darren Hart <dvhart@infradead.org>,
	Andy Shevchenko <andy@infradead.org>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	"# 3.4.x" <stable@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	X86 ML <x86@kernel.org>
Subject: Re: [PATCH v2] x86/sme: Explicitly map new EFI memmap table as encrypted
Date: Wed, 1 Dec 2021 08:05:58 -0600	[thread overview]
Message-ID: <15ceb556-0b56-2833-206e-0cf9b9d2cb45@amd.com> (raw)
In-Reply-To: <f939e968-149f-1caf-c1fb-5939eafae31c@amd.com>

On 10/27/21 12:04 PM, Tom Lendacky wrote:
> 
> 
> On 10/27/21 11:59 AM, Ard Biesheuvel wrote:
>> On Wed, 27 Oct 2021 at 18:56, Borislav Petkov <bp@alien8.de> wrote:
>>>
>>> On Wed, Oct 27, 2021 at 05:14:35PM +0200, Ard Biesheuvel wrote:
>>>> I could take it, but since it will ultimately go through -tip anyway,
>>>> perhaps better if they just take it directly? (This will change after
>>>> the next -rc1 though)
>>>>
>>>> Boris?
>>>
>>> Yeah, I'm being told this is not urgent enough to rush in now so you
>>> could queue it into your fixes branch for 5.16 once -rc1 is out and send
>>> it to Linus then. The stable tag is just so it gets backported to the
>>> respective trees.
>>>
>>> But if you prefer I should take it, then I can queue it after -rc1.
>>> It'll boil down to the same thing though.
>>>
>>
>> No, in that case, I can take it myself.
>>
>> Tom, does that work for you?
> 
> Yup, that works for me. Thanks guys!

I don't see this in any tree yet, so just a gentle reminder in case it 
dropped off the radar.

Thanks,
Tom

> 
> Tom
> 
>>

  reply	other threads:[~2021-12-01 14:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 17:02 [PATCH v2] x86/sme: Explicitly map new EFI memmap table as encrypted Tom Lendacky
2021-10-27 15:11 ` Tom Lendacky
2021-10-27 15:14   ` Ard Biesheuvel
2021-10-27 16:56     ` Borislav Petkov
2021-10-27 16:59       ` Ard Biesheuvel
2021-10-27 17:04         ` Tom Lendacky
2021-12-01 14:05           ` Tom Lendacky [this message]
2021-12-03 10:30             ` Ard Biesheuvel
2021-12-03 16:22               ` Tom Lendacky
2021-12-03 18:13                 ` Ard Biesheuvel

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=15ceb556-0b56-2833-206e-0cf9b9d2cb45@amd.com \
    --to=thomas.lendacky@amd.com \
    --cc=andy@infradead.org \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=dvhart@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mingo@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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