From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
stable@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] x86/sme: Explicitly map new EFI memmap table as encrypted
Date: Tue, 14 Dec 2021 14:40:36 +0100 [thread overview]
Message-ID: <Ybie1MoJE3v95NOx@kroah.com> (raw)
In-Reply-To: <b50c83fa-ada2-23e8-c797-767190c08934@amd.com>
On Tue, Dec 14, 2021 at 05:54:56AM -0600, Tom Lendacky wrote:
> On 12/14/21 3:09 AM, Greg Kroah-Hartman wrote:
> > On Sat, Dec 11, 2021 at 11:19:00AM -0600, Tom Lendacky wrote:
>
> >
> > This seems to cause config warnings as reported here:
> > https://lore.kernel.org/r/CA+G9fYsEQCjOi_58WcMb4i-2t1Gv=KjPuWa6L792YAZF=zzinw@mail.gmail.com
> > and:
> > https://lore.kernel.org/r/CA+G9fYuCFSbLMarXOnapUXN_NRgQMkjfr_rSTPjzBJQ-FT-Q3g@mail.gmail.com
> >
> > so I will be dropping this commit from the 4.14, 4.19, and 5.4 trees.
> > Can you please fix this up and resend?
>
> Yes, I'll look into this.
Looks like 5.4.y is working ok, I'll leave the change in there.
thanks,
greg k-h
next prev parent reply other threads:[~2021-12-14 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 17:19 [PATCH] x86/sme: Explicitly map new EFI memmap table as encrypted Tom Lendacky
2021-12-12 13:20 ` Greg Kroah-Hartman
2021-12-14 9:09 ` Greg Kroah-Hartman
2021-12-14 11:54 ` Tom Lendacky
2021-12-14 13:40 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-20 18:02 Tom Lendacky
2021-10-21 13:21 ` Tom Lendacky
2021-10-22 14:48 ` Ard Biesheuvel
2021-10-22 16:21 ` Tom Lendacky
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=Ybie1MoJE3v95NOx@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ardb@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=stable@vger.kernel.org \
--cc=thomas.lendacky@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