linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <florian@openwrt.org>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Greg KH <greg@kroah.com>, Anca Emanuel <anca.emanuel@gmail.com>,
	Elvis Dowson <elvis.dowson@mac.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	openwrt-devel@lists.openwrt.org
Subject: Re: Forked android kernel development from linux kernel mainline
Date: Tue, 9 Nov 2010 14:27:09 +0100	[thread overview]
Message-ID: <201011091427.09050.florian@openwrt.org> (raw)
In-Reply-To: <AANLkTik=UWwRLOaHMfVifYiQPpSwoYuA6J1EoL5BOgJY@mail.gmail.com>

Arnaud,

On Sunday 07 November 2010 22:44:48 Arnaud Lacombe wrote:
> Hi,
> 
> On Sun, Nov 7, 2010 at 10:57 AM, Greg KH <greg@kroah.com> wrote:
> > [...]
> 
> 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.

So I do agree the situation is not the best because we still maintain too many 
patches in the OpenWrt repository, especially since the added value of OpenWrt 
do not only resides in the kernel patches for a specific target.

Please understand that we are just human beings and right now, ar71xx is 
becoming more and more present on the wireless routers market, that's why 
developpers (Imre and Gabor) are being kept busy making this target work fine 
on all of the routers out there (and it's not just about 1 or 2 models, we are 
talking about nearly 50, all of these with different hardware integration, thus 
challenges).

The fact that we are using subversion is purely gratuitous, remember this is 
just a tool after all. The flat structure that we have, and the per-kernel 
version patches still makes it easy for people to pick whatever they need from 
our tree. Certainly this is not ideal, but no major stopper.

> 
> I'm still stuck to use their 2.6.32 to use my AR71xx-based (MIPS)
> boards, just this part is +15kloc.

2.6.36 support for ar71xx is out there since Oct 8th.
--
Florian

  parent reply	other threads:[~2010-11-09 13:27 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 [this message]
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=201011091427.09050.florian@openwrt.org \
    --to=florian@openwrt.org \
    --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).