All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, gerickson@nuovations.com,
	dougthompson@xmission.com
Subject: Re: [PATCH 1/1] edac: new ppc4xx driver module
Date: Mon, 9 Feb 2009 13:12:00 -0800	[thread overview]
Message-ID: <20090209131200.f2e5fb6f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090209210119.GF2297@yoda.jdub.homelinux.org>

On Mon, 9 Feb 2009 16:01:19 -0500
Josh Boyer <jwboyer@linux.vnet.ibm.com> wrote:

> On Fri, Feb 06, 2009 at 11:49:47AM -0800, Andrew Morton wrote:
> >On Fri, 06 Feb 2009 11:40:41 -0800
> >Grant Erickson <gerickson@nuovations.com> wrote:
> >
> >> On 1/30/09 2:05 PM, Andrew Morton wrote:
> >> > On Fri, 30 Jan 2009 09:54:42 -0700 dougthompson@xmission.com wrote:
> >> >> From: Grant Erickson <gerickson@nuovations.com>
> >> > 
> >> > Perhaps a powerpc mailing list should have been cc'ed?
> >> 
> >> The first round patch went to Doug, the BlueSmoke (EDAC) mailing list and
> >> the Linux/PowerPC mailing list. However, because the original patch was
> >> split in two, subsequent revisions of just the EDAC piece went to Doug and
> >> BlueSmoke. Doug then forwarded it to linux-kernel.
> >> 
> >> What's the preferred sign-off, ACK chain for this subsystem? Through
> >> PowerPC/4xx or PowerPC GIT upstream or through you and -mm upstream?
> >
> >I don't trust those guys ;)
> 
> I might take offense to that, but it seems that there aren't too many people
> in general that you trust, so I guess that's fine. ;)
> 
> (And while you may or may not be joking, if there's something that I've done
> to be considered not trustworthy then please let me know.)

Every kernel cycle there are literally hundreds of patches which slip
through subsystem tree maintainers' fingers.  Patches which I unlose
for them.  Heaven knows how many patches get lost on mailing lists
which I don't read.

My mistrust is widespread and well-placed ;)

> >I'd merge it via -mm, while cc'ing various random powerpc personalities.
> 
> Erm, ok.  Since there doesn't appear to be an EDAC git tree for -next I
> guess that makes sense.  I'll try to review the most recent version in the
> next few days.

Thanks.

      reply	other threads:[~2009-02-09 21:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 16:54 [PATCH 1/1] edac: new ppc4xx driver module dougthompson
2009-01-30 22:05 ` Andrew Morton
2009-02-06 19:40   ` Grant Erickson
2009-02-06 19:49     ` Andrew Morton
2009-02-09 21:01       ` Josh Boyer
2009-02-09 21:12         ` Andrew Morton [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=20090209131200.f2e5fb6f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dougthompson@xmission.com \
    --cc=gerickson@nuovations.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.