From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752811AbcGAKJX (ORCPT ); Fri, 1 Jul 2016 06:09:23 -0400 Received: from mail-wm0-f68.google.com ([74.125.82.68]:36150 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752201AbcGAKJU (ORCPT ); Fri, 1 Jul 2016 06:09:20 -0400 Date: Fri, 1 Jul 2016 09:59:58 +0200 From: Ingo Molnar To: Masanari Iida Cc: corbet@lwn.net, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com Subject: Re: [PATCH] [linux-next] Doc: x86: Fix typo in x86 Message-ID: <20160701075958.GA15093@gmail.com> References: <20160701034601.30308-1-standby24x7@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160701034601.30308-1-standby24x7@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Masanari Iida wrote: > This patch fix some spelling typo found in > Documentation/x86. > > Signed-off-by: Masanari Iida > --- > Documentation/x86/intel_mpx.txt | 6 +++--- > Documentation/x86/tlb.txt | 4 ++-- > Documentation/x86/x86_64/machinecheck | 2 +- > 3 files changed, 6 insertions(+), 6 deletions(-) > > diff --git a/Documentation/x86/intel_mpx.txt b/Documentation/x86/intel_mpx.txt > index 1a5a12184a35..4c40a85ae2b1 100644 > --- a/Documentation/x86/intel_mpx.txt > +++ b/Documentation/x86/intel_mpx.txt > @@ -45,7 +45,7 @@ is how we expect the compiler, application and kernel to work together. > MPX-instrumented. > 3) The kernel detects that the CPU has MPX, allows the new prctl() to > succeed, and notes the location of the bounds directory. Userspace is > - expected to keep the bounds directory at that locationWe note it > + expected to keep the bounds directory at that location We note it So this documentation fix kept the much more obvious typo in place: that sentence is missing a period ... I fixed that in the patch, but next time please read the text you are patching ... Thanks, Ingo