Skip to contentSkip to conversation

amd64_edac: EDAC module for AMD64

RFC PATCH Doug Thompson 1 participant 1 message May 8, 2009

lore
Share & tools
lore
#0 lore raw
Quoted 49 lines · Ingo Molnar

From: Ingo Molnar <[email protected]>
Subject: Re: [RFC PATCH 00/21 v3] amd64_edac: EDAC module for AMD64
To: "Andrew Morton" <[email protected]>
Cc: "Borislav Petkov" <[email protected]>, [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Date: Thursday, May 7, 2009, 3:18 PM

Quoted 2 lines · Andrew Morton

On Thu, 7 May 2009 16:38:07 +0200
Borislav Petkov <[email protected]>

Quoted 4 lines · wrote:
Quoted 4 lines

Hi,

On Thu, May 07, 2009 at 04:27:24PM +0200, Ingo

Quoted 1 line · Molnar
Quoted 1 line
Quoted 1 line

Regarding workflow, the arch/x86 bits look

good to me now, so you've

Quoted 5 lines
Quoted 5 lines
Quoted 1 line

got my Acked-by for that.

Cool, thanks.

Does that mean you're going to pick that one

or...

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

Most of the EDAC patches are hosted in
-mm, so we could carry them in the x86 tree

separately as well and

Quoted 1 line
Quoted 1 line
Quoted 1 line

export it to linux-next so that -mm will

have it automatically.

Quoted 5 lines
Quoted 3 lines

is the bunch going through Andrew as a whole?

I could.  But there's negligible overlap with

other EDAC work so

Quoted 1 line

we might as well merge this via IngoTrees or directly

from your

Quoted 1 line

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.

Quoted 6 lines

[ 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

I agree, if it removes a burden from some

doug t