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]

Message-ID: <20101107001341.4e39c631@lxorguk.ukuu.org.uk>
Date:	Sun, 7 Nov 2010 00:13:41 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Ted Ts'o" <tytso@....edu>
Cc:	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 Sat, 6 Nov 2010 20:03:48 -0400
"Ted Ts'o" <tytso@....edu> wrote:

> On Sat, Nov 06, 2010 at 04:52:26PM -0700, david@...g.hm wrote:
> > also, none of these other patches resulted in device drivers
> > developed for a distro being incompatible with mainline.
> 
> What, people can't delete a couple of single lines of code before
> submitting the device driver upstream to mainline?

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.

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