From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andi Kleen <ak@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -v6 for 2.6.32] x86: MCE: Re-implement MCE log ring buffer as per-CPU ring buffer
Date: Fri, 21 Aug 2009 10:41:19 +0900 [thread overview]
Message-ID: <4A8DFB3F.40309@jp.fujitsu.com> (raw)
In-Reply-To: <1250736679.5337.540.camel@yhuang-dev.sh.intel.com>
Huang Ying wrote:
> Re-implement MCE log ring buffer as per-CPU ring buffer for better
> scalability.
>
(snip)
> ChangeLog:
>
> v6:
>
> - Rebased on latest x86-tip.git/x86/mce + x86/tip
Does this mean your patch is based on a local branch you merged?
Why not on tip/x86/mce alone as usual?
What branch are you requesting this patch to be applied to?
Thanks,
H.Seto
next prev parent reply other threads:[~2009-08-21 1:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 2:51 [PATCH -v6 for 2.6.32] x86: MCE: Re-implement MCE log ring buffer as per-CPU ring buffer Huang Ying
2009-08-21 1:41 ` Hidetoshi Seto [this message]
2009-08-21 2:29 ` Huang Ying
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=4A8DFB3F.40309@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.com \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=ying.huang@intel.com \
/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