All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Gross <agross@codeaurora.org>
To: Tim Bird <tim.bird@sonymobile.com>
Cc: Bjorn Andersson <Bjorn.Andersson@sonymobile.com>,
	ohad@wizery.com,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	jhugo@codeaurora.org, s-anna@ti.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Frank Rowand <frowand.list@gmail.com>
Subject: Re: [PATCH v6 2/2] hwspinlock: qcom: Add support for Qualcomm HW, Mutex block
Date: Wed, 11 Mar 2015 17:15:13 -0500	[thread overview]
Message-ID: <20150311221513.GA27985@qualcomm.com> (raw)
In-Reply-To: <5500A8BE.2060601@sonymobile.com>

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

  reply	other threads:[~2015-03-11 22:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 20:42 [PATCH v6 2/2] hwspinlock: qcom: Add support for Qualcomm HW, Mutex block Tim Bird
2015-03-11 20:42 ` Tim Bird
2015-03-11 22:15 ` Andy Gross [this message]
2015-03-12  8:16   ` Ohad Ben-Cohen
2015-03-12 15:26     ` Tim Bird
  -- strict thread matches above, loose matches on Subject: below --
2015-02-27 22:30 [PATCH v6 1/2] DT: hwspinlock: Add binding documentation for Qualcomm hwmutex Bjorn Andersson
2015-02-27 22:30 ` [PATCH v6 2/2] hwspinlock: qcom: Add support for Qualcomm HW Mutex block Bjorn Andersson
2015-02-27 22:30   ` Bjorn Andersson
2015-03-11 21:09   ` Andy Gross
2015-03-12 19:31   ` Lina Iyer
2015-03-12 19:43     ` Andy Gross
2015-03-12 19:55       ` Lina Iyer
2015-03-18 16:10         ` Bjorn Andersson
2015-03-18 15:55     ` Bjorn Andersson
2015-03-18 16:45       ` Lina Iyer
2015-03-18 21:59         ` Bjorn Andersson
2015-03-12 22:29   ` Lina Iyer
2015-03-18 16:12     ` Bjorn Andersson
2015-03-18 19:41       ` Lina Iyer
2015-03-16 22:38   ` Jeffrey Hugo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150311221513.GA27985@qualcomm.com \
    --to=agross@codeaurora.org \
    --cc=Bjorn.Andersson@sonymobile.com \
    --cc=akpm@linux-foundation.org \
    --cc=frowand.list@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jhugo@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=s-anna@ti.com \
    --cc=tim.bird@sonymobile.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.