public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/4] x86: corruption-check: fix some style issues
Date: Mon, 27 Oct 2008 18:11:39 +0100	[thread overview]
Message-ID: <20081027171139.GE19476@elte.hu> (raw)
In-Reply-To: <20081005120705.02492d44@infradead.org>


* Arjan van de Ven <arjan@infradead.org> wrote:

> From: Arjan van de Ven <arjan@linux.intel.com>
> Date: Sun, 5 Oct 2008 11:08:10 -0700
> Subject: [PATCH] x86: corruption-check: fix some style issues
> 
> Before moving the code to it's own file, fix some style issues
> in the corruption check code.
> 
> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
> ---
>  arch/x86/kernel/setup.c |    9 +++++----
>  1 files changed, 5 insertions(+), 4 deletions(-)

i've picked up your fixes into tip/x86/corruption-check:

b43d196: x86: corruption-check: some post-move cleanups
304e629: x86: corruption check: run the corruption checks from a work queue
6784f7d: x86: corruption check: move the corruption checks into their own file
04d2aac: x86: corruption-check: fix some style issues

thanks Arjan!

	Ingo

      parent reply	other threads:[~2008-10-27 17:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-05 19:07 [PATCH 1/4] x86: corruption-check: fix some style issues Arjan van de Ven
2008-10-05 19:08 ` [PATCH 2/4] x86: corruption check: move the corruption checks into their own file Arjan van de Ven
2008-10-05 19:09 ` [PATCH 3/4] x86: corruption check: run the corruption checks from a work queue Arjan van de Ven
2008-10-05 19:35   ` Vegard Nossum
2008-10-05 19:09 ` [PATCH 4/4] x86: corruption-check: some post-move cleanups Arjan van de Ven
2008-10-27 17:11 ` 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=20081027171139.GE19476@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --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