From: Tim Bird <tim.bird@sonymobile.com>
To: Ohad Ben-Cohen <ohad@wizery.com>, Andy Gross <agross@codeaurora.org>
Cc: "\"Andersson, Björn\"" <Bjorn.Andersson@sonymobile.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"Jeffrey Hugo" <jhugo@codeaurora.org>,
"Anna, Suman" <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: Thu, 12 Mar 2015 08:26:21 -0700 [thread overview]
Message-ID: <5501B01D.2050208@sonymobile.com> (raw)
In-Reply-To: <CAK=WgbZVOOGuo+1LsHU8t7DuTs2bA4F9bQuH7qCAqwE9W-qyxg@mail.gmail.com>
On 03/12/2015 01:16 AM, Ohad Ben-Cohen wrote:
> On Thu, Mar 12, 2015 at 12:15 AM, Andy Gross <agross@codeaurora.org> wrote:
>> 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.
>
> I definitely plan to get this and Suman's work merged upstream.
>
> As Andy mentioned I'm doing this in my off time and unfortunately this
> means I'm sometimes less available than I wish I was. Not too long ago
> this activity (as well as the maintainership of remoteproc and rpmsg)
> was graciously sponsored by one of the silicon vendors but that is no
> longer the case.
>
> Anyway I plan to get to this in the weekend, hope to push things forward.
Thanks for the response. It's helpful to know your status.
-- Tim
next prev parent reply other threads:[~2015-03-12 15:26 UTC|newest]
Thread overview: 17+ 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 22:15 ` Andy Gross
2015-03-12 8:16 ` Ohad Ben-Cohen
2015-03-12 15:26 ` Tim Bird [this message]
-- 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-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=5501B01D.2050208@sonymobile.com \
--to=tim.bird@sonymobile.com \
--cc=Bjorn.Andersson@sonymobile.com \
--cc=agross@codeaurora.org \
--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 \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).