From: Borislav Petkov <bp@alien8.de>
To: Daniel J Blueman <daniel@numascale-asia.com>
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, 4 Dec 2012 17:01:56 +0100 [thread overview]
Message-ID: <20121204160156.GH4369@liondog.tnic> (raw)
In-Reply-To: <50BDC140.8060004@numascale-asia.com>
On Tue, Dec 04, 2012 at 05:24:16PM +0800, Daniel J Blueman wrote:
> It works well on fam10h and fam15h boxes, with and without Numaconnect.
Good, thanks for testing.
I will send it upstream after the upcoming merge window closes since it
is too late for this one now and I wouldn't want to rush it if it is not
necessary to do so and it hasn't seen enough testing in linux-next and
-tip trees. Which means that it will end up in 3.9; I hope that is OK
with you guys.
Thanks.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-12-04 16:02 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 [this message]
2013-02-19 14:40 ` Daniel J Blueman
2013-02-19 14:59 ` Borislav Petkov
2013-02-19 15:08 ` Daniel J Blueman
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=20121204160156.GH4369@liondog.tnic \
--to=bp@alien8.de \
--cc=daniel@numascale-asia.com \
--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