From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: New mailing list specifically for embedded PowerPC development
Date: Sun, 26 Sep 2004 09:12:31 +1000 [thread overview]
Message-ID: <1096153951.475.23.camel@gaston> (raw)
In-Reply-To: <20040925175739.GJ2107@smtp.west.cox.net>
On Sun, 2004-09-26 at 03:57, Tom Rini wrote:
> On Sat, Sep 25, 2004 at 01:01:56PM +1000, Benjamin Herrenschmidt wrote:
>
> > On Sat, 2004-09-25 at 12:59, Benjamin Herrenschmidt wrote:
> > > I specifically asked for the split.
> >
> > Oh, and another reason, which, though, is also a signal/noise
> > ratio matter. I expect most patches addressing ppc32 to be CCed
> > to linuxppc-dev. This is important for distro people to keep track
> > of bug fixes that went in after the kernel version they decided to
> > freeze on.
>
> Are you referring to the pmac distro people, the embedded distro people
> or the 'other' distro people here?
The non-embedded ones
Ben.
next prev parent reply other threads:[~2004-09-25 23:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 6:46 New mailing list specifically for embedded PowerPC development Stephen Rothwell
2004-09-23 23:30 ` Tom Rini
2004-09-24 0:31 ` Brian Waite
2004-09-24 1:22 ` Hollis Blanchard
2004-09-24 3:23 ` Tom Rini
2004-09-24 5:52 ` Dan Malek
2004-09-24 16:41 ` Tom Rini
2004-09-25 2:59 ` Benjamin Herrenschmidt
2004-09-25 3:01 ` Benjamin Herrenschmidt
2004-09-25 3:08 ` Owen Stampflee
2004-09-25 18:01 ` Tom Rini
2004-09-25 18:10 ` Matt Porter
2004-09-25 17:57 ` Tom Rini
2004-09-25 23:12 ` Benjamin Herrenschmidt [this message]
2004-09-25 18:08 ` Matt Porter
2004-09-24 1:07 ` Eugene Surovegin
2004-09-24 16:48 ` Matt Porter
2004-09-25 18:56 ` Matt Porter
2004-09-26 12:13 ` Stephen Rothwell
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=1096153951.475.23.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=trini@kernel.crashing.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).