[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimyZ75ZMsYYJnD32bpKObAfbBNJ0wUF42H-axV1@mail.gmail.com>
Date: Sat, 6 Nov 2010 17:20:45 -0700
From: Janakiram Sistla <janakiram.sistla@...il.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>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Forked android kernel development from linux kernel mainline
On Sat, Nov 6, 2010 at 5:13 PM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> 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.
>
I think the developers target for andriod kernel more than the
mainline.The biggest point of the hour is whether the device works for
Android Eclair, Android Froyo and not the see their patches in linux
kernel unfortunately.
Regards,
Ram.
--
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/
Powered by blists - more mailing lists