From mboxrd@z Thu Jan 1 00:00:00 1970 From: "luke.leighton" Subject: Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1)) Date: Fri, 7 Jun 2013 09:06:24 +0100 Message-ID: References: <51AFA6DD.3000202@wwwdotorg.org> <1370469574.18839.33.camel@localhost> <1370475609.20454.44.camel@localhost> <1370477958.20454.68.camel@localhost> <51B085C6.3000605@gmail.com> <51B19046.5040401@gmail.com> Reply-To: Linux on small ARM machines Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <51B19046.5040401@gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: arm-netbook-bounces@lists.phcomp.co.uk Sender: "arm-netbook" To: Linux on small ARM machines Cc: debian-arm@lists.debian.org, devicetree-discuss , Linux Kernel Mailing List , ARM Linux Mailing List , debian-kernel@lists.debian.org List-Id: devicetree@vger.kernel.org On Fri, Jun 7, 2013 at 8:48 AM, Vladimir Pantelic wrote: > luke.leighton wrote: >> >> On Thu, Jun 6, 2013 at 1:51 PM, Vladimir Pantelic >> 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.