linux-kernel - Re: HTC Dream aka. t-mobile g1 support

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]

Message-ID: <20090611123455.6c066db6@lxorguk.ukuu.org.uk>
Date:	Thu, 11 Jun 2009 12:34:55 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Pavel Machek <pavel@....cz>, David Miller <davem@...emloft.net>,
	linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk, ibm@...roid.com,
	swetland@...gle.com, san@...roid.com, rlove@...gle.com
Subject: Re: HTC Dream aka. t-mobile g1 support

> Now, ask yourself this question: why should I have to be the one to
> review things like ARM <-> DSP communication channel code?  Hint: I

Because you claim to be ARM maintainer and you force all the ARM stuff to
go via you ? 

We have the -next tree these days so if you cut ARM back to common core
shared ARM code and all the platform people had their own maintainer (at
least those who are competent to do so which is a fair share of them)
then you could resolve any collisions in -next. There will probably be a
few explosions on the way because code developed under such a tight
control model tends to have poor separation in places nobody thought
about but they'll fix pretty fast.

If you don't want to be reviewing some of the stuff then restructure
things so that they don't go through you and you are not the gatekeeper
for them.

Alan
--
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/