From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] ppc: add support for new powerbooks
Date: Thu, 10 Nov 2005 17:06:33 +1100 [thread overview]
Message-ID: <1131602793.24637.159.camel@gaston> (raw)
In-Reply-To: <20051109220022.264437f8.akpm@osdl.org>
> Well yes, that's a generic problem with subsystem trees. I suppose one
> could enforce processes which prevent it from happening.
I think the right process is to go through the linuxppc[64]-dev list(s)
first, maybe CC lkml when it's not strictly arch gore, and then hop from
there to -git. We also have a nice patch tracking system scanning those
lists, I suppose I need to fix my own habits of bypassing all of that
stuff :)
> OK, well please think about it. It's not a ton of work at this end at
> present, but a) you lazy bums don't ack most of the things I cc you on, so
> it's rather open-loop and I don't know whether I'm merging wrong patches
> and b) there's now increasing potential for patches in -mm to clash with
> patches in Paul's git tree.
>
> The latter can be solved easily enough: I add Paul's git tree to the -mm
> lineup.
I think going through the -git tree always makes sense and I've doing
doing that for my own production, I'll route patches that I'm acking
that way too from now on.
I'm keeping the liberty of bombing you & linus directly when I think
it's an important bug fix late in the rc cycle though :)
Ben.
next prev parent reply other threads:[~2005-11-10 6:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 7:22 [PATCH] ppc: add support for new powerbooks Olof Johansson
2005-11-09 9:00 ` Benjamin Herrenschmidt
2005-11-10 5:38 ` Andrew Morton
2005-11-10 5:40 ` Benjamin Herrenschmidt
2005-11-10 6:00 ` Andrew Morton
2005-11-10 6:06 ` Benjamin Herrenschmidt [this message]
2005-11-10 6:08 ` Paul Mackerras
2005-11-10 6:29 ` Andrew Morton
2005-11-10 16:44 ` Olof Johansson
2005-11-10 17:12 ` Kumar Gala
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=1131602793.24637.159.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).