From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, the arch/x86 maintainers <x86@kernel.org>
Subject: [GIT PULL] x86/sev updates for v6.15
Date: Sat, 22 Mar 2025 13:08:22 +0100 [thread overview]
Message-ID: <Z96oNui7G1OTIyLg@gmail.com> (raw)
Linus,
Please pull the latest x86/sev Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-sev-2025-03-22
# HEAD: f0373cc0907ca7918266a507d6b3b5d75ee839ba x86/sev: Simplify the code by removing unnecessary 'else' statement
x86/sev updates for v6.15:
- Improve sme_enable() PIC build robustness (Kevin Loughlin)
- Simplify vc_handle_msr() a bit (Peng Hao)
Thanks,
Ingo
------------------>
Kevin Loughlin (1):
x86/sev: Add missing RIP_REL_REF() invocations during sme_enable()
Peng Hao (1):
x86/sev: Simplify the code by removing unnecessary 'else' statement
arch/x86/coco/sev/core.c | 3 +--
arch/x86/mm/mem_encrypt_identity.c | 4 ++--
2 files changed, 3 insertions(+), 4 deletions(-)
next reply other threads:[~2025-03-22 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 12:08 Ingo Molnar [this message]
2025-03-25 6:08 ` [GIT PULL] x86/sev updates for v6.15 pr-tracker-bot
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=Z96oNui7G1OTIyLg@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox