linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Spraul <wolfgang@sharism.cc>
To: OpenWrt Development List <openwrt-devel@lists.openwrt.org>
Cc: Arnaud Lacombe <lacombar@gmail.com>, Greg KH <greg@kroah.com>,
	Elvis Dowson <elvis.dowson@mac.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Anca Emanuel <anca.emanuel@gmail.com>
Subject: Re: [OpenWrt-Devel] Forked android kernel development from linux kernel mainline
Date: Tue, 9 Nov 2010 13:51:29 +0000	[thread overview]
Message-ID: <20101109135129.GE14380@asus.wolf> (raw)
In-Reply-To: <201011091427.09050.florian@openwrt.org>

Florian and Greg,

> > Just a small comment to say that Android is not the only one (but
> > certainly the most visible, and thus easiest to bash on) not making
> > effort to get their stuff in mainline. OpenWRT people are also
> > maintaining their fork of the kernel, without even using git, and not
> > contributing much to mainline (I'm certainly mistaken on that last
> > comment).
> 
> You are a bit rude and mistaking at the same time. We did contribute back TI 
> AR7, Mikrotik RB532, RDC R-321x, IXP4xx to name a few and a lot of various 
> patches on different related projects.

I'm speaking as a bystander here, but Lars-Peter Clausen took an enormous
effort to get an entire new SoC, Ingenic's XBurst 4740, into mainline
Linux, using the OpenWrt patch system as his development/staging area.
A lot of that work was merged mainline in 2.6.36, some more is coming.

I think the mainline quality standards are high (nothing wrong with that),
so it's not easy to get stuff up to that level. And there is not exactly
much of a pull force either, if I may say so.

I have worked on numerous projects, platforms and build systems over
the years. The OpenWrt people and tools are some of the most upstream
oriented and best ways to get upstream I have seen.

The next big thing I will try to lend a helping hand to will be the
kernel.org inclusion of the Milkymist SoC.
A fairly clean and constantly re-based kernel is here
https://github.com/tmatsuya/linux-2.6
Linux 2.6.36+ is already booting, now it 'only' needs to go mainline ;-)
http://lists.milkymist.org/pipermail/devel-milkymist.org/2010-October/000979.html

Anybody mainline care to pull directly? That would be awesome. Otherwise
my next best bet would be to go to OpenWrt first, hack it into SVN
patches, then go from there. At least OpenWrt cares a lot to produce
buildable and bootable images at any time, that's an excellent way to
go for bigger and better things.

>From the perspective of someone looking from mainline, I can understand
the frustration over not seeing a git repo that one can pull from at
any time. But from the outside it looks a bit different. Patches are
sometimes forced to live outside mainline for a long long time, years.
And in those years the way OpenWrt is dealing with patches is still a
very effective system to avoid bitrot.

my 2c,
Wolfgang

  reply	other threads:[~2010-11-09 13:51 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
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               ` Wolfgang Spraul [this message]
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=20101109135129.GE14380@asus.wolf \
    --to=wolfgang@sharism.cc \
    --cc=anca.emanuel@gmail.com \
    --cc=elvis.dowson@mac.com \
    --cc=greg@kroah.com \
    --cc=lacombar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openwrt-devel@lists.openwrt.org \
    /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).