From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>, Ingo Molnar <mingo@kernel.org>
Cc: Borislav Petkov <bp@amd64.org>,
EDAC devel <linux-edac@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] AMD thresholding fixes
Date: Wed, 25 Apr 2012 18:57:31 +0200 [thread overview]
Message-ID: <20120425165730.GB18314@x1.osrc.amd.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F170F3C53@ORSMSX104.amr.corp.intel.com>
On Wed, Apr 25, 2012 at 04:49:52PM +0000, Luck, Tony wrote:
> > If there are no issues, I'll add the queue to linux-next (I don't see a
> > branch from ras.git in linux-next, btw, which is strange).
>
> Patches so far have been flowing from "ras" to "tip" to "linus". It
> hasn't quite been clear how linux-next fits into this. If we export
> to -next, then are we planning on sending those directly to linus,
> bypassing tip?
That's actually a good point. Once in -tip, they're seeing linux-next
anyway.
Ok, Ingo, what would you guys rather have:
* ras tree -> linux-next -> we send pull request to Linus
or
* ras tree -> -tip -> linux-next (automatically due to tip daily merges)
-> you send pull request to Linus
I guess I'm fine with both, second one makes us even lazier :)
Thanks.
--
Regards/Gruss,
Boris.
prev parent reply other threads:[~2012-04-25 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 15:52 [PATCH 0/3] AMD thresholding fixes Borislav Petkov
2012-04-25 15:52 ` [PATCH 1/3] x86, MCE, AMD: Make APIC LVT thresholding interrupt optional Borislav Petkov
2012-04-25 15:52 ` [PATCH 2/3] x86, MCE, AMD: Hide interrupt_enable sysfs node Borislav Petkov
2012-04-25 15:52 ` [PATCH 3/3] x86, MCE, AMD: Disable error thresholding bank 4 on some models Borislav Petkov
2012-04-25 16:49 ` [PATCH 0/3] AMD thresholding fixes Luck, Tony
2012-04-25 16:57 ` Borislav Petkov [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=20120425165730.GB18314@x1.osrc.amd.com \
--to=bp@alien8.de \
--cc=bp@amd64.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tony.luck@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