From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: Simon Arlott <simon@fire.lp0.eu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
trivial@kernel.org
Subject: Re: [discuss] [PATCH] spelling fixes: arch/x86_64/
Date: Sat, 12 May 2007 18:25:26 +0200 [thread overview]
Message-ID: <200705121825.26430.ak@suse.de> (raw)
In-Reply-To: <4644C783.3090805@simon.arlott.org.uk>
> +++ b/arch/x86_64/kernel/signal.c
> @@ -411,7 +411,7 @@ static void do_signal(struct pt_regs *regs)
>
> signr = get_signal_to_deliver(&info, &ka, regs, NULL);
> if (signr > 0) {
> - /* Reenable any watchpoints before delivering the
> + /* Re-enable any watchpoints before delivering the
reenable gets >140k google hits so it seems to be an really used word.
Similar with upto.
-Andi
next prev parent reply other threads:[~2007-05-12 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 19:44 [PATCH] spelling fixes: arch/x86_64/ Simon Arlott
2007-05-12 16:25 ` Andi Kleen [this message]
2007-05-13 1:27 ` [discuss] " James Cloos
2007-05-13 8:14 ` Robert Dewar
2007-05-13 13:47 ` Alan Cox
2007-05-14 0:36 ` James Cloos
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=200705121825.26430.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simon@fire.lp0.eu \
--cc=trivial@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox