linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: david@lang.hm
To: "Ted Ts'o" <tytso@mit.edu>
Cc: 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: Sat, 6 Nov 2010 16:52:26 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1011061646170.29342@asgard.lang.hm> (raw)
In-Reply-To: <20101106234029.GC2935@thunk.org>

On Sat, 6 Nov 2010, Ted Ts'o wrote:

> On Sat, Nov 06, 2010 at 09:40:34PM +0200, Anca Emanuel wrote:
>> I think you need to see this: https://review.source.android.com/#change,18761
>> And this: http://galaxytab.samsungmobile.com/
>
> What about them?  Yes, the Android developers are pushing changes to
> mainstream where it makes sense; they were doing this before the
> wakelocks contrversy, and they're continuing to do it now.  But in the
> case of wakelocks, it may be that it's going to have to be a case of
> "agree to disagree".
>
> All distributions, including Red Hat and SLES has in the shipped
> product with patches that have never hit mainstream, and in some
> cases, will never get merged with mainstream.  A good example in the
> past was the 4G/4G patch.  Another one, which is still on-going, is
> the Systemtap/utrace patches.  Yet no one is killing megawatts worth
> of electrons about how Red Hat and SLES are forking the kernel.  They
> push patches upstream where they can, and where they can't --- they do
> what they need to do to satisify and delight their customers.
>
> (Heck, Sony is still using a 2.2 kernel for some of their products
> with a huge bunch of patches and no one is toasting them for forking
> the kernel....)

the difference is that these other patches that you are talking about do 
not result in incompatible userspace (or at least, they don't except for 
very specialied apps).

also, none of these other patches resulted in device drivers developed for 
a distro being incompatible with mainline.

I think that the concerns from technical folks (as opposed to 
journalists/bloggers) would go down drastically if there was some 
acceptable way for the incompatible bits (like wakelocks) could be 
stubbed out so that the rest of the things could be moved easily.

David Lang

> Move along, there's nothing to see.  Other that money for
> journalists/bloggers who are gunning for advertising clicks by
> whipping up controversy where IMHO, none deserves to exist.
>
> 					- Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2010-11-07  0:00 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 [this message]
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
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=alpine.DEB.2.00.1011061646170.29342@asgard.lang.hm \
    --to=david@lang.hm \
    --cc=anca.emanuel@gmail.com \
    --cc=elvis.dowson@mac.com \
    --cc=greg@kroah.com \
    --cc=janakiram.sistla@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).