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 13:12:20 +0200 [thread overview]
Message-ID: <e2e108260805010412g2f69bc4dh7b639aab3f6fafcb@mail.gmail.com> (raw)
In-Reply-To: <1209636359.25560.512.camel@pmac.infradead.org>
On Thu, May 1, 2008 at 12:05 PM, David Woodhouse <dwmw2@infradead.org> wrote:
> On Thu, 2008-05-01 at 11:55 +0200, Bart Van Assche wrote:
>> 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.
>
> The I²C list would be the best place to send such a patch. You could
> also copy it to the linux-embedded list if it's likely to be of interest
> to a reasonable proportion of "embedded" developers, but that wouldn't
> be the primary route into Linus' tree for most things.
>
> I can't really see any way to make that clear in the MAINTAINERS file
> that wouldn't be clumsy and just as confusing -- I think it'll work out
> just fine by itself. Do you have a concrete proposal?
The information present in the current MAINTAINERS file is such that
given the name(s) of the source files affected by a patch, one can
look up the appropriate mailing list(s) and maintainer(s) to send the
patch to. Information about embedded maintainer(s) is different: it's
not about maintaining specific source files but about general
discussions with regard to kernel changes for embedded systems. Maybe
there should be two sections in the MAINTAINERS file, one for
maintainers of specific source trees and another section for
coordinators of specific usage scenario's of the Linux kernel ?
Bart.
next prev parent reply other threads:[~2008-05-01 11:12 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
2008-05-01 10:05 ` David Woodhouse
2008-05-01 11:12 ` Bart Van Assche [this message]
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=e2e108260805010412g2f69bc4dh7b639aab3f6fafcb@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
all inboxes | Powered by JetHome®