linux-kernel - Re: Forked android kernel development from linux kernel mainline

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:	Tue, 9 Nov 2010 16:30:43 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Ted Ts'o <tytso@....edu>, david@...g.hm,
	Anca Emanuel <anca.emanuel@...il.com>,
	Greg KH <greg@...ah.com>, Elvis Dowson <elvis.dowson@....com>,
	Janakiram Sistla <janakiram.sistla@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Forked android kernel development from linux kernel mainline

On Sun, Nov 07, 2010 at 12:13:41AM +0000, Alan Cox wrote:

> I've always wondered that but never seen a good answer from the Android
> people as to why they don't push the stuff without the wakelock bits and
> just keep "add wakelock" patches for those as they do for the core kernel
> stuff they hack about.

Much of this code has other serious issues (eg, code quality or being
written for out of date kernel APIs) which prevents it being merged
without other work.

There are also some other areas where Android introduced random API
variance, though none of them terribly important.
--
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/