From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Ted Ts'o" <tytso@mit.edu>,
david@lang.hm, Anca Emanuel <anca.emanuel@gmail.com>,
Greg KH <greg@kroah.com>, Elvis Dowson <elvis.dowson@mac.com>,
Janakiram Sistla <janakiram.sistla@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Forked android kernel development from linux kernel mainline
Date: Wed, 10 Nov 2010 21:38:21 +0100 [thread overview]
Message-ID: <201011102138.22213.rjw@sisk.pl> (raw)
In-Reply-To: <20101110135458.GB1553@ucw.cz>
On Wednesday, November 10, 2010, Pavel Machek wrote:
> On Sat 2010-11-06 20:03:48, Ted Ts'o wrote:
> > On Sat, Nov 06, 2010 at 04:52:26PM -0700, david@lang.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? Here's the world's
> > tiniest violin playing, "my heart bleeds for you"....
>
> Deleting couple single liners is not a problem. Cleaning up 100KLoC
> patch for mainline *is* a problem.
>
> I know, I tried to do that work. Even getting it to staging quality
> was hard, and it was recently dropped due to security holes.
>
> Unfortunately google uses wakelocks as an excuse for not cleaning up
> stuff... "because readding those few lines would be too hard".
Actually, this isn't a good excuse any more as of 2.6.37-rc1. You can
basically replace wakelocks with wakeup sources and go ahead.
Thanks,
Rafael
next prev parent reply other threads:[~2010-11-10 20:39 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 18:18 Forked android kernel development from linux kernel mainline Elvis Dowson
2010-11-02 21:25 ` Janakiram Sistla
2010-11-06 18:12 ` Greg KH
2010-11-06 19:22 ` Ted Ts'o
2010-11-06 19:40 ` Anca Emanuel
2010-11-06 23:40 ` Ted Ts'o
2010-11-06 23:52 ` david
2010-11-07 0:03 ` Ted Ts'o
2010-11-07 0:13 ` Alan Cox
2010-11-07 0:20 ` Janakiram Sistla
2010-11-09 16:30 ` Mark Brown
2010-11-07 0:20 ` david
2010-11-10 13:54 ` Pavel Machek
2010-11-10 20:38 ` Rafael J. Wysocki [this message]
2011-01-11 14:33 ` Pavel Machek
2010-11-06 23:42 ` Janakiram Sistla
2010-11-06 23:09 ` Greg KH
2010-11-07 0:24 ` Randy Dunlap
2010-11-07 8:38 ` Elvis Dowson
2010-11-07 11:44 ` Anca Emanuel
2010-11-07 15:57 ` Greg KH
2010-11-07 20:06 ` Elvis Dowson
2010-11-07 21:31 ` Greg KH
2010-11-07 21:46 ` Arnaud Lacombe
2010-11-07 21:47 ` Arnaud Lacombe
2010-11-09 18:10 ` Elvis Dowson
2010-11-09 18:24 ` Greg KH
2010-11-09 18:37 ` Elvis Dowson
2010-11-09 18:42 ` david
2010-11-09 18:52 ` Elvis Dowson
2010-11-09 20:55 ` Ted Ts'o
2010-11-09 22:32 ` Alan Cox
2010-11-10 0:35 ` Ted Ts'o
2010-11-10 9:53 ` Florian Mickler
2010-11-10 20:55 ` Alan Cox
2010-11-07 21:44 ` Arnaud Lacombe
2010-11-07 21:59 ` Greg KH
2010-11-07 23:09 ` Arnaud Lacombe
2010-11-08 1:42 ` Greg KH
2010-11-08 2:22 ` Arnaud Lacombe
2010-11-09 13:27 ` Florian Fainelli
2010-11-11 0:33 ` Roland Dreier
2010-11-11 0:40 ` Thomas Gleixner
2010-11-12 3:15 ` Roland Dreier
2010-11-12 10:26 ` Florian Fainelli
2010-11-11 0:47 ` Greg KH
2010-11-11 11:21 ` Florian Fainelli
2010-11-12 3:17 ` Roland Dreier
2010-11-11 11:18 ` Florian Fainelli
2010-11-09 13:27 ` Florian Fainelli
2010-11-09 13:51 ` [OpenWrt-Devel] " Wolfgang Spraul
2010-11-13 3:06 ` Arnaud Lacombe
2010-11-15 17:34 ` Stefan Monnier
2010-11-16 6:23 ` Brian Swetland
2010-11-16 7:02 ` Anca Emanuel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201011102138.22213.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=anca.emanuel@gmail.com \
--cc=david@lang.hm \
--cc=elvis.dowson@mac.com \
--cc=greg@kroah.com \
--cc=janakiram.sistla@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).