linux-kernel - Re: [PATCH 1/1] Embedded Maintainer(s), linux-embedded@...r list

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 1 May 2008 13:12:20 +0200
From:	"Bart Van Assche" <bart.vanassche@...il.com>
To:	"David Woodhouse" <dwmw2@...radead.org>
Cc:	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	"Paul Gortmaker" <paul.gortmaker@...driver.com>,
	linux-embedded@...r.kernel.org, linux-kernel@...r.kernel.org,
	"Tim Bird" <tim.bird@...sony.com>
Subject: Re: [PATCH 1/1] Embedded Maintainer(s), linux-embedded@...r list

On Thu, May 1, 2008 at 12:05 PM, David Woodhouse <dwmw2@...radead.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/