From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: [PATCH] taa fix
Date: Thu, 7 Nov 2019 16:04:35 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1911071604010.4256@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20191107145947.ueaz4vyf2dkikgxz@treble>
On Thu, 7 Nov 2019, speck for Josh Poimboeuf wrote:
> On Thu, Nov 07, 2019 at 02:49:52PM +0100, speck for Borislav Petkov wrote:
> > Make that "Fix printing" and you're good.
>
> Fair enough. I'll go with
>
> x86/speculation/taa: Fix printing of TAA_MSG_SMT on IBRS_ALL CPUs
No need to resend. I already fixed it locally.
Thanks,
tglx
prev parent reply other threads:[~2019-11-07 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 2:26 [MODERATED] [PATCH] taa fix Josh Poimboeuf
2019-11-07 2:41 ` [MODERATED] " Tyler Hicks
2019-11-07 9:25 ` Borislav Petkov
2019-11-07 13:47 ` Josh Poimboeuf
2019-11-07 13:49 ` Borislav Petkov
2019-11-07 14:59 ` Josh Poimboeuf
2019-11-07 15:04 ` Thomas Gleixner [this message]
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=alpine.DEB.2.21.1911071604010.4256@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).