mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86/sev for v7.0-rc1
Date: Wed, 11 Feb 2026 10:50:13 +0100	[thread overview]
Message-ID: <20260211095013.GAaYxQ1XWSOfnrtuEo@fat_crate.local> (raw)
In-Reply-To: <177078052792.4176860.4001765608553456080.pr-tracker-bot@kernel.org>

On Wed, Feb 11, 2026 at 03:28:47AM +0000, pr-tracker-bot@kernel.org wrote:
> The pull request you sent on Tue, 10 Feb 2026 15:29:27 +0100:
> 
> > ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/tip/tip tags/x86_sev_for_v7.0_rc1
> 
> has been merged into torvalds/linux.git:
> https://git.kernel.org/torvalds/c/ca8f421ea0d3f1d39f773e14f68f93c978e470ef

"    [ TLA translation service: 'SEV' is AMD's 'Secure Encrypted
      Virtualization' and SVSM is an ETLA ('Enhanced TLA') for 'Secure
      VM Service Module'.
    
      Some of us have trouble keeping track of this all and need all the
      help we can get ]"

Only half-jokingly I'm going to suggest that maybe we should start documenting
all that TLA gunk somewhere in Documentation/, similar to how specs have their
"Conventions and Definitions" chapters at the beginning where they give some
basic blurb about acronyms used throughout the document so that readers are on
the same page, more or less...

:-)

-- 
Regards/Gruss,
    Boris.

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

  reply	other threads:[~2026-02-11  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 14:29 Borislav Petkov
2026-02-11  3:28 ` pr-tracker-bot
2026-02-11  9:50   ` Borislav Petkov [this message]
2026-02-11 17:19     ` Linus Torvalds
2026-02-11 20:13       ` Borislav Petkov

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=20260211095013.GAaYxQ1XWSOfnrtuEo@fat_crate.local \
    --to=bp@alien8.de \
    --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

all inboxes | Powered by JetHome®