On Wed, Mar 11, 2015 at 01:42:38PM -0700, Tim Bird wrote: <snip>
> I'm pretty anxious about this one, as my current work has a dependency on it. > Virtually the entirety of the QualComm SOC work is dependent on this > because it's needed by the interprocessor communication framework > and the regulator driver. > > I assume we're waiting on the response from Ohad about getting this upstream? > It's been almost 2 weeks with no reply. > > Ohad - do you plan to do anything with this patch? We seem to be at an > impasse > (once again). With Suman's patches and this, the ball is in Ohad's court. I believe Ohad does this work in his off time as it is unpaid work. > > This is the 6th attempt over the course of the last year and a half to get > this hwspinlock code mainlined. Should we just not use the hwspinlock > framework? > > What are our options going forward? Not sure, aside from landing this somewhere else. But that has it's own inherent issues. -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
