From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Walker Subject: the future of qualcomm SoC in linux Date: Fri, 1 Nov 2013 10:11:13 -0700 Message-ID: <20131101171112.GA17267@fifo99.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from fifo99.com ([67.223.236.141]:51835 "EHLO fifo99.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753107Ab3KARLX (ORCPT ); Fri, 1 Nov 2013 13:11:23 -0400 Content-Disposition: inline Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: davidb@codeaurora.org, bryanh@codeaurora.org Cc: arnd@arndb.de, olof@lixom.net, khilman@deeprootsystems.com, linux-arm-msm@vger.kernel.org David, Bryan, In general this community wants all code maintained. Your intentions seem to be that you want to push code, but you want to orphan it fairly quickly after you push the code. I know this is true having worked with both of you and many of your developers, and recent events seem to prove it. It's fine if you don't want to maintain the code you push, but it's better for us as a community if some one does maintains the code long term (10-15 years). Linux also fosters community development so that people with devices can submit patches or add extensions to existing code. It's my believe that you don't want that, and have no intentions of supporting it for any of your platforms or for any device that is created with your chips. Since both of you seem un-willing to do these things, I suggesting this compromise. I maintain the code long term for all Qualcomm platforms new and old, you submit patches to me. If you don't want me to do this, or don't trust me to do it, that's fine too just find someone else willing to maintain all the code long term. Daniel