linux-kernel - Re: [OpenWrt-Devel] Forked android kernel development from linux kernel mainline

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101109135129.GE14380@asus.wolf>
Date:	Tue, 9 Nov 2010 13:51:29 +0000
From:	Wolfgang Spraul <wolfgang@...rism.cc>
To:	OpenWrt Development List <openwrt-devel@...ts.openwrt.org>
Cc:	Arnaud Lacombe <lacombar@...il.com>, Greg KH <greg@...ah.com>,
	Elvis Dowson <elvis.dowson@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Anca Emanuel <anca.emanuel@...il.com>
Subject: Re: [OpenWrt-Devel] Forked android kernel development from linux
 kernel mainline

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
--
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/