From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from p4fea4eb5.dip0.t-ipconnect.de ([79.234.78.181] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fGvGF-0006PL-SX for speck@linutronix.de; Fri, 11 May 2018 01:46:12 +0200 Date: Fri, 11 May 2018 01:46:11 +0200 (CEST) From: Thomas Gleixner Subject: Re: [PATCH v4 6/8] L1TFv4 3 In-Reply-To: <20180510232649.GK13616@tassilo.jf.intel.com> Message-ID: References: <524e068e6b7286121da0b3979bb20fd5a2b3fe38.1525900921.git.ak@linux.intel.com> <20180510232649.GK13616@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Thu, 10 May 2018, speck for Andi Kleen wrote: > > > + > > > + /* > > > + * This is extremely unlikely to happen because systems near always have far > > > > s/near/almost/ > > There are some very rare systems where it may, mainly SGI UV. Sure, but that does not change the fact that 'near always' should be 'almost always' :) Maybe rephrase it to: This is extremely unlikely to happen because almost all systems have..... Thanks, tglx