[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wj9dTa=N-QBAoUir7J-yYhfjmSFrs3e=QMLJPRcR-nn8A@mail.gmail.com>
Date: Wed, 11 Feb 2026 09:19:05 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Borislav Petkov <bp@...en8.de>
Cc: x86-ml <x86@...nel.org>, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] x86/sev for v7.0-rc1
On Wed, 11 Feb 2026 at 01:50, Borislav Petkov <bp@...en8.de> wrote:
>
> Only half-jokingly I'm going to suggest that maybe we should start documenting
> all that TLA gunk somewhere in Documentation/
I don't think that's a bad idea, but it doesn't actually solve the
problem for me - I still have to look up the TLA somewhere.
At that point, the difference between "file in Documentation/" and
"just google it to remind me" is pretty much zero.
Of course, for most people, this likely isn't much of a problem.
Most people probably work primarily in one area and just don't deal
with lots of different architectures and see pull requests for lots of
different driver subsystems.
And so when you work in that one particular area, you end up knowing
the relevant TLA's intimately and don't even have to think about it.
While the TLA's from other subsystems don't much matter, and is
"somebody else's problem".
But then somebody like me, who typically sees lots of different pull
requests from many different areas, without being deeply involved with
any of those areas, and still feels the need to actually know what is
going on, has to look those things up.
Or - and hey, this is possible - I just have the mental attention span
of a slightly damaged rodent, and so I can't remember even the
simplest TLA.
Because there's strong evidence for that last point: I have to look up
those things _every_ single time, because I just can't seem to ever
remember the whole "Intel calls their version XYZ, AMD calls it ABC,
and arm64 calls it ".
Linus
Powered by blists - more mailing lists