From: Daniel J Blueman <daniel@numascale-asia.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
H Peter Anvin <hpa@zytor.com>,
Steffen Persvold <sp@numascale.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4 v8] AMD64 EDAC: Fix type usage in NB IDs and memory ranges
Date: Tue, 19 Feb 2013 23:08:19 +0800 [thread overview]
Message-ID: <51239563.2050900@numascale-asia.com> (raw)
In-Reply-To: <20130219145947.GK26623@pd.tnic>
On 19/02/2013 22:59, Borislav Petkov wrote:
> On Tue, Feb 19, 2013 at 10:40:26PM +0800, Daniel J Blueman wrote:
>> Alas your merges missed the v3.8 merge window, but it looks like your
>> v3.9 pull request has dropped these patches [1].
>>
>> Any chance you can get them in during this merge window?
>
> They should go in anytime now. They're in tip:x86/platform and Ingo is
> sending pull requests to Linus as we speak. Since they touch x86 code I
> asked x86 guys to send them upstream instead of me.
Superb; thanks for your help Boris and Ingo!
Daniel
--
Daniel J Blueman
Principal Software Engineer, Numascale Asia
next prev parent reply other threads:[~2013-02-19 15:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 8:44 [PATCH 3/4 v8] AMD64 EDAC: Fix PCI function lookup Daniel J Blueman
2012-11-30 8:44 ` [PATCH 4/4 v8] AMD64 EDAC: Fix type usage in NB IDs and memory ranges Daniel J Blueman
2012-11-30 17:17 ` Borislav Petkov
2012-12-04 9:24 ` Daniel J Blueman
2012-12-04 16:01 ` Borislav Petkov
2013-02-19 14:40 ` Daniel J Blueman
2013-02-19 14:59 ` Borislav Petkov
2013-02-19 15:08 ` Daniel J Blueman [this message]
2013-01-22 16:53 ` [tip:x86/platform] amd64_edac: " tip-bot for Daniel J Blueman
2012-11-30 11:27 ` [PATCH 3/4 v8] AMD64 EDAC: Fix PCI function lookup Borislav Petkov
2013-01-22 16:52 ` [tip:x86/platform] amd64_edac: " tip-bot for Daniel J Blueman
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=51239563.2050900@numascale-asia.com \
--to=daniel@numascale-asia.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sp@numascale.com \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox