From: Joe Perches <joe@perches.com>
To: Jean Carlo Machado <contato@jeancarlomachado.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix typos on kernel-hacking docs
Date: Fri, 03 Nov 2017 16:26:49 -0700 [thread overview]
Message-ID: <1509751609.15520.52.camel@perches.com> (raw)
In-Reply-To: <20171103225529.5441-1-contato@jeancarlomachado.com.br>
On Fri, 2017-11-03 at 20:55 -0200, Jean Carlo Machado wrote:
> ---
> Documentation/kernel-hacking/hacking.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/kernel-hacking/hacking.rst b/Documentation/kernel-hacking/hacking.rst
[]
> @@ -288,7 +288,7 @@ userspace.
> -[Yes, this moronic interface makes me cringe. The flamewar comes up
> +[Yes, this moronic interface makes me cringe. The flame war comes up
[]
> -them. They are reentrant; saving the previous state in their one
> +them. They are re-entrant; saving the previous state in their one
[]
> -them. They are reentrant; if soft interrupts were disabled before, they
> +them. They are re-entrant; if soft interrupts were disabled before, they
[]
> -Most registerable structures have an owner field, such as in the
> +Most registrable structures have an owner field, such as in the
[]
> - Make sure you put your name and EMail address at the top of any files
> + Make sure you put your name and Email address at the top of any files
I think none of these are improvements.
prev parent reply other threads:[~2017-11-03 23:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 22:55 [PATCH] fix typos on kernel-hacking docs Jean Carlo Machado
2017-11-03 23:26 ` Joe Perches [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=1509751609.15520.52.camel@perches.com \
--to=joe@perches.com \
--cc=contato@jeancarlomachado.com.br \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.