linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Stephen Rothwell <sfr@ozlabs.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: New mailing list specifically for embedded PowerPC development
Date: Sat, 25 Sep 2004 11:56:29 -0700	[thread overview]
Message-ID: <20040925115629.C11580@home.com> (raw)
In-Reply-To: <20040923164655.0472a8b9.sfr@ozlabs.org>; from sfr@ozlabs.org on Thu, Sep 23, 2004 at 04:46:55PM +1000

On Thu, Sep 23, 2004 at 04:46:55PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After some representations, I have created linuxppc-embedded@ozlabs.org
> for the discussion of all things to do with the development of Linux on
> embedded PowerPC platforms.
> 
> General Linux on PowerPC development discussions should, of course, remain
> on this list.

Let's try this a different way. :) Could you please add the following
text to the mailman list pages? Any objections? I think this will clarify
list usage as BenH would like it.

linuxppc-dev
------------
This is the Linux on PowerPC developers' mailing list. It is
free and open to all those interested in development of Linux
on PowerPC hardware, but discussions/patches should pertain to
software development for the kernel core ppc32 support and
CHRP/Pmac/PReP platforms.   Any discussions/patches regarding
embedded procesoors/platforms should be directed to the
linuxppc-embedded list.

Patches are welcomed, but please refrain from posting excessively
large ones (40K is currently the limit for the entire message).
Large patches should be made available at an accessible FTP or
web site and the URL posted to this list. The list owner reserves
the right to implement filtering of list messages, unsubscribe
offenders, and/or otherwise prevent posting of messages to enforce
the list charter.
-----------------

linuxppc-embedded
-----------------
This is the Linux on PowerPC embedded developers' mailing list.
It is free and open to all those interested in development
of Linux on embedded PowerPC hardware, but discussions/patches
should pertain to software development for the kernel core ppc32
embedded processor support and any driver/chip/board support for
ppc32 based embedded systems. Any discussions/patches regarding
generic core ppc32 support should be directed to the linuxppc-dev
list.

Patches are welcomed, but please refrain from posting excessively
large ones (40K is currently the limit for the entire message).
Large patches should be made available at an accessible FTP or
web site and the URL posted to this list. The list owner reserves
the right to implement filtering of list messages, unsubscribe
offenders, and/or otherwise prevent posting of messages to enforce
the list charter.
-----------------

Regards,
Matt

  parent reply	other threads:[~2004-09-25 18:56 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
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 [this message]
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=20040925115629.C11580@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfr@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).