From: Owen Stampflee <ostampflee@terrasoftsolutions.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: New mailing list specifically for embedded PowerPC development
Date: Fri, 24 Sep 2004 20:08:16 -0700 [thread overview]
Message-ID: <1096081696.2453.22.camel@beast.terraplex.com> (raw)
In-Reply-To: <1096081315.576.15.camel@gaston>
> 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.
>
> That will simply not happen if the embedded traffic is mixed in
Agreed. I've already missed a patch or two in this big mess.
There is just way too much noise about various embedded issues. Myself
and many others simply don't want to know about latest and greatest
serial/ethernet/foo driver for the latest SoC out of Freescale and it
makes it really really difficult to follow the occasional thread about
stuff we do care about.
Embedded people, think about your complaints if the ppc64 list were
merged too... there would be a whole bunch of email you don't care about
on a list that should be fairly focused.
Cheers,
Owen
next prev parent reply other threads:[~2004-09-25 3:41 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 [this message]
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
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=1096081696.2453.22.camel@beast.terraplex.com \
--to=ostampflee@terrasoftsolutions.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 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).