From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
"Paul Gortmaker" <paul.gortmaker@windriver.com>,
linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org,
"Tim Bird" <tim.bird@am.sony.com>
Subject: Re: [PATCH 1/1] Embedded Maintainer(s), linux-embedded@vger list
Date: Thu, 1 May 2008 11:55:36 +0200 [thread overview]
Message-ID: <e2e108260805010255v6b728998i7d4952cc8fec28cb@mail.gmail.com> (raw)
In-Reply-To: <1209577483.25560.405.camel@pmac.infradead.org>
On Wed, Apr 30, 2008 at 7:44 PM, David Woodhouse <dwmw2@infradead.org> wrote:
> Add Paul and myself, and the linux-embedded list, to MAINTAINERS.
>
> Signed-off-by: David Woodhouse <dwmw2@infradead.org>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index bca09ed..3650ed1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1550,6 +1550,14 @@ M: raisch@de.ibm.com
> L: general@lists.openfabrics.org
> S: Supported
>
> +EMBEDDED LINUX
> +P: Paul Gortmaker
> +M: paul.gortmaker@windriver.com
> +P David Woodhouse
> +M: dwmw2@infradead.org
> +L: linux-embedded@vger.kernel.org
> +S: Maintained
> +
> EMULEX LPFC FC SCSI DRIVER
> P: James Smart
> M: james.smart@emulex.com
It's great that more attention is being paid to the use of Linux in
embedded systems. And the MAINTAINERS file is probably the right file
to add the above information. But I'm afraid that the way the above
information is formatted will cause confusion. As an example, recently
there was a driver added to the Linux kernel for the PCF8575 chip.
This is an I2C chip that is only used in embedded systems. Regarding
driver review, should any such drivers be sent to the I2C mailing
list, the embedded mailing list or both ? The MAINTAINERS file should
be clear on this.
Bart.
next prev parent reply other threads:[~2008-05-01 9:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 17:42 [PATCH 0/1] " David Woodhouse
2008-04-30 17:44 ` [PATCH 1/1] " David Woodhouse
2008-05-01 9:55 ` Bart Van Assche [this message]
2008-05-01 10:05 ` David Woodhouse
2008-05-01 11:12 ` Bart Van Assche
2008-04-30 18:22 ` [PATCH 0/1] " Andi Kleen
2008-04-30 19:11 ` David Woodhouse
2008-06-23 17:22 ` Denys Vlasenko
2008-06-23 18:57 ` Sam Ravnborg
2008-06-23 19:12 ` Denys Vlasenko
2008-06-23 19:33 ` Sam Ravnborg
[not found] ` <48190B5F.9010505@am.sony.com>
[not found] ` <20080501095822.GL20451@one.firstfloor.org>
2008-05-01 10:02 ` David Woodhouse
2008-05-01 10:41 ` Andi Kleen
2008-05-02 15:00 ` Pekka Enberg
2008-05-02 20:01 ` Eduard - Gabriel Munteanu
2008-05-02 20:14 ` Andrew Morton
2008-05-02 20:33 ` Eduard - Gabriel Munteanu
2008-05-02 20:53 ` Andrew Morton
2008-05-03 22:24 ` Randy Dunlap
2008-05-05 1:52 ` Andrew Morton
2008-06-23 17:28 ` Denys Vlasenko
2008-06-23 17:45 ` Adrian Bunk
2008-06-23 18:19 ` Denys Vlasenko
2008-06-23 19:05 ` Tim Bird
2008-06-25 9:50 ` James Chapman
2008-06-25 15:41 ` Adrian Bunk
2008-04-30 18:26 ` Josh Boyer
2008-04-30 18:43 ` David Woodhouse
2008-04-30 18:45 ` Josh Boyer
2008-04-30 23:34 ` Adrian Bunk
2008-05-01 7:04 ` David Woodhouse
2008-05-02 11:58 ` Kristoffer Ericson
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=e2e108260805010255v6b728998i7d4952cc8fec28cb@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tim.bird@am.sony.com \
--cc=torvalds@linux-foundation.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
Powered by JetHome