From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: stable@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH 1/2] x86: Make ARCH_USE_MEMREMAP_PROT a generic Kconfig symbol
Date: Fri, 17 Dec 2021 15:54:46 +0100 [thread overview]
Message-ID: <YbyktpQbbhImNkbe@kroah.com> (raw)
In-Reply-To: <20aa49e158bf5ad18df99febdac0a93790e1a746.1639685720.git.thomas.lendacky@amd.com>
On Thu, Dec 16, 2021 at 02:15:19PM -0600, Tom Lendacky wrote:
> From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> commit ce9084ba0d1d8030adee7038ace32f8d9d423d0f upstream
> to be applied to 4.14.
All now queued up, thnaks.
greg k-h
next prev parent reply other threads:[~2021-12-17 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 20:15 [PATCH 1/2] x86: Make ARCH_USE_MEMREMAP_PROT a generic Kconfig symbol Tom Lendacky
2021-12-16 20:15 ` [PATCH 2/2] x86/sme: Explicitly map new EFI memmap table as encrypted Tom Lendacky
2021-12-17 14:54 ` Greg Kroah-Hartman [this message]
2021-12-16 20:16 [PATCH 1/2] x86: Make ARCH_USE_MEMREMAP_PROT a generic Kconfig symbol 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=YbyktpQbbhImNkbe@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ardb@kernel.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;
as well as URLs for NNTP newsgroup(s).