historical-speck.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 2/2] more sampling fun 2
Date: Tue, 25 Feb 2020 08:44:25 -0600	[thread overview]
Message-ID: <20200225144425.pz3mqjdyzt57ptu3@treble> (raw)
In-Reply-To: <nycvar.YFH.7.76.2002251520060.13129@cbobk.fhfr.pm>

On Tue, Feb 25, 2020 at 03:23:31PM +0100, speck for Jiri Kosina wrote:
> On Tue, 25 Feb 2020, speck for Josh Poimboeuf wrote:
> 
> > Well, I see it the opposite way.  Those jumbles of letters do actually
> > mean something.  I still call them "MDS", "L1TF", "SSBD".  If you google
> 
> BTW as a sidenote -- I think you actually nicely demonstrated all the 
> confusion coming from all these crazy acronyms.
> 
> While MDS and L1TF are the names of the actual vulnerability, SSBD is 
> acronym for the mitigation.

Right - we should have just called it "ssb=", to match the Intel
acronym, instead of creating our own.

-- 
Josh

  reply	other threads:[~2020-02-25 14:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 17:31 [MODERATED] Re: [PATCH 2/2] more sampling fun 2 Konrad Rzeszutek Wilk
2020-02-24 18:17 ` [MODERATED] " Borislav Petkov
2020-02-24 21:39   ` mark gross
2020-02-24 23:10     ` [MODERATED] " Borislav Petkov
2020-02-25  1:26       ` Josh Poimboeuf
2020-02-25 10:46         ` Borislav Petkov
2020-02-25 14:18           ` Josh Poimboeuf
2020-02-25 14:23             ` Jiri Kosina
2020-02-25 14:44               ` Josh Poimboeuf [this message]
2020-02-25 14:59             ` Borislav Petkov
2020-02-26 20:20               ` Josh Poimboeuf
2020-02-26 21:16                 ` Thomas Gleixner
2020-02-26 22:19                   ` [MODERATED] " Konrad Rzeszutek Wilk
     [not found] <c5bae80efe4694c81d9cbbce633a2228086a330c.158215=?utf-8?q?2322?= .git.mgross@linux.intel.com>
2020-02-20 19:06 ` Ben Hutchings
2020-02-20 19:35   ` mark gross
2020-02-21 22:25     ` mark gross

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=20200225144425.pz3mqjdyzt57ptu3@treble \
    --to=jpoimboe@redhat.com \
    --cc=speck@linutronix.de \
    /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).