From: Shawn Guo <shawnguo@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Kiran Gunda <kgunda@codeaurora.org>,
sboyd@codeaurora.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Abhijeet Dharmapurikar <adharmap@codeaurora.org>,
David Collins <collinsd@codeaurora.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
linux-arm-msm-owner@vger.kernel.org
Subject: Re: [PATCH V2] spmi: pmic-arb: Enforce the ownership check optionally
Date: Mon, 28 Aug 2017 22:08:01 +0800 [thread overview]
Message-ID: <20170828140759.GC3525@dragon> (raw)
In-Reply-To: <20170828115328.GA26757@kroah.com>
On Mon, Aug 28, 2017 at 01:53:28PM +0200, Greg KH wrote:
> On Fri, Aug 18, 2017 at 08:58:29PM +0530, Kiran Gunda wrote:
> > The peripheral ownership check is not necessary on single master
> > platforms. Hence, enforce the peripheral ownership check optionally.
> >
> > Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>
> > Tested-by: Shawn Guo <shawnguo@kernel.org>
> > ---
> > v2:
> > Fixed the commit message.
> > Added Shawn's 'Tested-by' tag.
> >
> > v1:
> > This patch depends on the below patch series. Please take this patch
> > along with this series.
> >
> > [PATCH V2 00/12]: spmi: pmic-arb: Support for HW v5 and other fixes
> >
> > Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.txt | 6 ++++++
> > drivers/spmi/spmi-pmic-arb.c | 7 ++++++-
> > 2 files changed, 12 insertions(+), 1 deletion(-)
>
> This doesn't apply on top of the other spmi patches I just added to my
> tree. Did I mess something up here?
Sorry, Greg. We should have told you that this patch is obsolete and
replaced by the one below, which you just applied to char-misc-testing.
spmi: pmic-arb: Move the ownership check to irq_chip callback
Shawn
prev parent reply other threads:[~2017-08-28 14:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 15:28 [PATCH V2] spmi: pmic-arb: Enforce the ownership check optionally Kiran Gunda
[not found] ` <1503070110-15018-1-git-send-email-kgunda-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-08-21 23:18 ` Stephen Boyd
2017-08-22 8:55 ` Shawn Guo
2017-08-22 20:31 ` Stephen Boyd
2017-08-23 12:57 ` kgunda
2017-08-24 12:18 ` Shawn Guo
2017-08-24 18:37 ` Stephen Boyd
2017-08-25 7:47 ` Shawn Guo
2017-08-25 23:18 ` Stephen Boyd
[not found] ` <20170825231818.GP21656-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-08-26 3:46 ` Shawn Guo
2017-08-30 21:02 ` Stephen Boyd
2017-08-31 8:37 ` Shawn Guo
2017-09-01 1:30 ` Stephen Boyd
[not found] ` <20170901013048.GK21656-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-09-01 3:00 ` Shawn Guo
2017-08-28 8:27 ` Fenglin Wu
[not found] ` <93b8935e-061f-ba3a-ee36-8ffbc8230bcc-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-08-28 14:47 ` Shawn Guo
2017-08-22 9:01 ` Shawn Guo
2017-08-28 11:53 ` Greg KH
2017-08-28 14:08 ` Shawn Guo [this message]
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=20170828140759.GC3525@dragon \
--to=shawnguo@kernel.org \
--cc=adharmap@codeaurora.org \
--cc=collinsd@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kgunda@codeaurora.org \
--cc=linux-arm-msm-owner@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
/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).