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 for Android: free password hash cracker in your pocket

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

Message-ID: <a55d774e0906110618k20cdccd5wd1655e5c3dbef6ec@mail.gmail.com>
Date:	Thu, 11 Jun 2009 06:18:15 -0700
From:	Brian Swetland <swetland@...gle.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Russell King - ARM Linux <linux@....linux.org.uk>,
	David Miller <davem@...emloft.net>, pavel@....cz,
	linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk, san@...roid.com,
	rlove@...gle.com
Subject: Re: HTC Dream aka. t-mobile g1 support

On Thu, Jun 11, 2009 at 5:54 AM, Alan Cox<alan@...rguk.ukuu.org.uk> wrote:
>
> Make your tree the core ARM code only, any other patches you don't
> accept. Aggressively push stuff out to platform code, and if people want
> to change core code "because our platform is different" make them extract
> it into the platform layer not carry it in the core bits.
>
> Nominate a bunch of people for the main ARM platforms. What they put into
> their platform specific trees goes direct from them to -next and if they
> trash their own platform thats their problem (and they can come to you
> for advice ;))
>
> Leave it to the platform people to push their driver code through the
> right channels.

This would seem to address a lot of the scalability issues, and from
what I can tell, it's pretty hard for somebody mucking stuff up in
arch/arm/mach-something/... to break arch/arm/mach-otherthing/...

I'd be thrilled to get the msm stuff in to the main tree and deal with
patches submitted against it (and the android stuff in staging seems
to show that people will start submitting patches against things if
it's in the mainline -- for example the binder patches that have
turned up, etc).

As far as what we're maintaining in the android-msm tree, there's:
generic android drivers -- most of which are already in staging thanks to Greg
arch/arm/mach-msm/... -- 7k (and soon 8k) SoC support
various msm drivers -- could be submitted via drivers/staging and the
usual review process
a couple small generic arm patches -- stuff that we should be
discussing in lakml
some generic linux patches -- Arve's pretty good about sending these
to lkml as they happen

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