From: Ingo Molnar <mingo@elte.hu>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Masami Hiramatsu <mhiramat@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86: trivial whitespace in kprobes.c
Date: Thu, 10 Jan 2008 13:44:58 +0100 [thread overview]
Message-ID: <20080110124458.GC15156@elte.hu> (raw)
In-Reply-To: <1199954157.19760.22.camel@brick>
* Harvey Harrison <harvey.harrison@gmail.com> wrote:
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
> ---
> Ingo, you could/should probably fold this into Masami's kprobe
> unification patch.
i applied this as a separate patch - better for whitespace changes to
not be mixed into unification patches.
Ingo
prev parent reply other threads:[~2008-01-10 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 8:35 [PATCH] x86: trivial whitespace in kprobes.c Harvey Harrison
2008-01-10 10:42 ` Masami Hiramatsu
2008-01-10 11:06 ` Masami Hiramatsu
2008-01-10 12:44 ` Ingo Molnar [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=20080110124458.GC15156@elte.hu \
--to=mingo@elte.hu \
--cc=harvey.harrison@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.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