From: Andi Kleen <andi@firstfloor.org>
To: x86@kernel.org
Cc: hpa@zytor.com, seto.hidetoshi@jp.fujitsu.com,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: *PING* Re: Please pull mce3-improvements tree
Date: Fri, 29 May 2009 20:38:18 +0200 [thread overview]
Message-ID: <87k53zeov9.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20090527202427.GA8073@basil.nowhere.org> (Andi Kleen's message of "Wed, 27 May 2009 22:24:27 +0200")
Andi Kleen <andi@firstfloor.org> writes:
> This is the x86 machine check improvements tree that I posted yesterday.
> I addressed the review comments and did some minor changes. I'm
> not reposting everything as patches because the changes are quite
> minor.
>
> This is all ready for merging now. Most of these patches
> are quite old and have been extensively reviewed.
>
> It is based on the mce3-32bitmerge tree that I offered earlier.
>
> Please merge this for 2.6.31
*PING* Please pull the three trees or provide comments.
Thanks,
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2009-05-29 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 20:24 Please pull mce3-improvements tree Andi Kleen
2009-05-29 18:38 ` Andi Kleen [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=87k53zeov9.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=x86@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.