linux-kernel - Re: 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: <jwvoc9qh4yp.fsf-monnier+gmane.comp.embedded.openwrt.devel@gnu.org>
Date:	Mon, 15 Nov 2010 12:34:15 -0500
From:	Stefan Monnier <monnier@....umontreal.ca>
To:	linux-kernel@...r.kernel.org
Subject: Re: Forked android kernel development from linux kernel mainline

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

It's not only that.  But Android in general is also a very poor citizen
w.r.t Free Software since it tends to be distributed in closed form for
devices that only work if you add proprietary code, and it supports
DRM-style nightmares.
It's not as dangerous to Free Software as the iphone, tho.

> 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).

I can assure you that the contributions are as frequent, important, and
significant as the OpenWRT can muster: they have very limited resources,
which is the main limitation.  But also because of those limited
resources, it's in their best interest to get things upstream.

Android is different since the company behind it made a conscious
decision to fork even though they have/had the resources necessary to
push their changes upstream.

        Stefan

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