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
| ||
|
Date: Fri, 7 Jun 2013 09:06:24 +0100 From: "luke.leighton" <luke.leighton@...il.com> To: Linux on small ARM machines <arm-netbook@...ts.phcomp.co.uk> Cc: debian-arm@...ts.debian.org, devicetree-discuss <devicetree-discuss@...abs.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, ARM Linux Mailing List <linux-arm-kernel@...ts.infradead.org>, debian-kernel@...ts.debian.org Subject: Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1)) On Fri, Jun 7, 2013 at 8:48 AM, Vladimir Pantelic <vladoman@...il.com> wrote: > luke.leighton wrote: >> >> On Thu, Jun 6, 2013 at 1:51 PM, Vladimir Pantelic <vladoman@...il.com> >> wrote: >> >>> 4 days? WTF? since when did setting an ultimatum to the kernel >>> community work? >> >> >> i was only informed of the opportunity 2 days ago, vladimir. this is >> an important meeting. of course the linux kernel community is >> entirely free to: >> >> * completely ignore this opportunity >> * continue to complain that soc vendors do not follow their >> unilaterally-decided rules > > > SoC vendors are free to join the discussion, and many SoC vendors are part > of the kernel community, so calling this unilateral is plain wrong. you're free to believe that, vladimir. i've explained why that hasn't happened, in prior messages. can we move forward, please? > >> 3 days remaining on the clock. > > > what catastrophic thing will happen when the time runs out? no catastrophe, vladimir: all that happens is that an opportunity is lost, and the result of that is that the situation remains as it is, with a major soc vendor being divorced from and isolated from the free software community, who will continue to have to shoulder the frustrating and isolated burden of responsibility of reworking "over-the-fence" kernel patches as best they can with the limited resources that they have. -- 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/
Powered by blists - more mailing lists