[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090507211859.GA28770@elte.hu>
Date: Thu, 7 May 2009 23:18:59 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Borislav Petkov <borislav.petkov@....com>, greg@...ah.com,
norsk5@...oo.com, tglx@...utronix.de, hpa@...or.com,
mchehab@...hat.com, aris@...hat.com, edt@....ca,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 00/21 v3] amd64_edac: EDAC module for AMD64
* Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Thu, 7 May 2009 16:38:07 +0200
> Borislav Petkov <borislav.petkov@....com> wrote:
>
> > Hi,
> >
> > On Thu, May 07, 2009 at 04:27:24PM +0200, Ingo Molnar wrote:
> > > Regarding workflow, the arch/x86 bits look good to me now, so you've
> > > got my Acked-by for that.
> >
> > Cool, thanks.
> >
> > Does that mean you're going to pick that one or...
> >
> > > Most of the EDAC patches are hosted in
> > > -mm, so we could carry them in the x86 tree separately as well and
> > > export it to linux-next so that -mm will have it automatically.
> >
> > is the bunch going through Andrew as a whole?
> >
>
> I could. But there's negligible overlap with other EDAC work so
> we might as well merge this via IngoTrees or directly from your
> tree.
If Doug and you agrees too then i have no problem (at all) with
Borislav carrying these bits in a separate tree, as long as he also
opens an edac-next branch for linux-next and asks Stephen to pull
it, and keeps it an append-mostly tree that isnt rebased.
[ I still have to do a finegrained review of this lot, a quick look
suggested i'll have a few minor things to note ;) ]
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists