From: Ingo Molnar <mingo@kernel.org>
To: Masanari Iida <standby24x7@gmail.com>
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
Date: Fri, 1 Jul 2016 09:59:58 +0200 [thread overview]
Message-ID: <20160701075958.GA15093@gmail.com> (raw)
In-Reply-To: <20160701034601.30308-1-standby24x7@gmail.com>
* Masanari Iida <standby24x7@gmail.com> wrote:
> This patch fix some spelling typo found in
> Documentation/x86.
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
> 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
next prev parent reply other threads:[~2016-07-01 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 3:46 [PATCH] [linux-next] Doc: x86: Fix typo in x86 Masanari Iida
2016-07-01 7:59 ` Ingo Molnar [this message]
2016-07-01 8:12 ` [tip:x86/urgent] x86/Documentation: Fix various typos in Documentation/x86/ files tip-bot for Masanari Iida
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=20160701075958.GA15093@gmail.com \
--to=mingo@kernel.org \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=standby24x7@gmail.com \
--cc=tglx@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