From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (193.142.43.55:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 07 Nov 2019 13:50:00 -0000 Received: from mx2.suse.de ([195.135.220.15] helo=mx1.suse.de) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1iSiAg-0006up-Nf for speck@linutronix.de; Thu, 07 Nov 2019 14:49:59 +0100 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 632BFAC8E for ; Thu, 7 Nov 2019 13:49:52 +0000 (UTC) Date: Thu, 7 Nov 2019 14:49:52 +0100 From: Borislav Petkov Subject: [MODERATED] Re: [PATCH] taa fix Message-ID: <20191107134952.GG4243@zn.tnic> References: <20191107022646.6h724wh4im5zxvw2@treble> <20191107092533.GA4243@zn.tnic> <20191107134714.ngsdeubldn3h45ig@treble> MIME-Version: 1.0 In-Reply-To: <20191107134714.ngsdeubldn3h45ig@treble> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable To: speck@linutronix.de List-ID: On Thu, Nov 07, 2019 at 07:47:14AM -0600, speck for Josh Poimboeuf wrote: > On Thu, Nov 07, 2019 at 10:25:33AM +0100, speck for Borislav Petkov wrote: > > On Wed, Nov 06, 2019 at 08:26:46PM -0600, speck for Josh Poimboeuf wrote: > > > From: Josh Poimboeuf > > > Subject: [PATCH] x86/speculation/taa: Fix TAA_MSG_SMT printk > >=20 > > Subject should be something like "Print TAA_MSG_SMT on IBRS_ALL CPUs > > too" or so. >=20 > The subject is indeed overly broad. Though I wanted to highlight that > it's a fix. How about >=20 > x86/speculation/taa: Fix TAA_MSG_SMT printk on IBRS_ALL CPUs >=20 > ? Make that "Fix printing" and you're good. Because it is not really fixing the printk but it is making it print again. But we're bikeshedding... :-) --=20 Regards/Gruss, Boris. SUSE Software Solutions Germany GmbH, GF: Felix Imend=C3=B6rffer, HRB 36809, = AG N=C3=BCrnberg --=20