From: Stephen Boyd <sboyd@codeaurora.org>
To: Kiran Gunda <kgunda@codeaurora.org>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V4 0/4]: spmi: pmic-arb: support for V5 HW and bug fixes
Date: Tue, 18 Jul 2017 15:17:09 -0700 [thread overview]
Message-ID: <20170718221709.GA18179@codeaurora.org> (raw)
In-Reply-To: <1500373265-12875-1-git-send-email-kgunda@codeaurora.org>
On 07/18, Kiran Gunda wrote:
> v4:
> * spmi: pmic-arb: add support for HW version 5
> Clean-up as per Stephen's comments
>
> v3:
> * spmi: pmic-arb: add support for HW version 5
> Modified #define INVALID (-1) to
> #define INVALID_EE 0xFF.
>
> v2:
> * spmi: pmic-arb: return __iomem pointer instead of offset
> Added Stephen's reviewed-by tag.
>
> * spmi: pmic-arb: fix a possible null pointer dereference
> Added Stephen's reviewed-by tag.
>
> * spmi: pmic-arb: add support for HW version 5
> Modified the pmic_arb_offset_v5 function to return the offset instead
> of passed by a pointer.
>
> * spmi: pmic-arb: Remove checking opc value not less than 0
> Added Stephen's reviewed-by tag.
> Added my sign-off tag.
>
> v1:
>
> This patch series add the support for pmic arbiter hardware v5 along with
> the few bug fixes and code cleanup.
>
> This patch series is dependent on the below patches and can be merged
> cleanly only after picking the below patches in to the tree.
Can you combine the two series? It's really confusing why there
are two patch series from you for the same driver. Presumably one
of the series needs to be applied before the other, so putting
them into one series makes that clear what the order is.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-07-18 22:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 10:21 [PATCH V4 0/4]: spmi: pmic-arb: support for V5 HW and bug fixes Kiran Gunda
2017-07-18 10:21 ` [PATCH V4 1/4] spmi: pmic-arb: return __iomem pointer instead of offset Kiran Gunda
2017-07-18 10:21 ` [PATCH V4 2/4] spmi: pmic-arb: fix a possible null pointer dereference Kiran Gunda
2017-07-18 10:21 ` [PATCH V4 3/4] spmi: pmic-arb: add support for HW version 5 Kiran Gunda
2017-07-18 22:47 ` Stephen Boyd
2017-07-18 10:21 ` [PATCH V4 4/4] spmi: pmic-arb: Remove checking opc value not less than 0 Kiran Gunda
2017-07-18 22:17 ` Stephen Boyd [this message]
2017-07-20 6:50 ` [PATCH V4 0/4]: spmi: pmic-arb: support for V5 HW and bug fixes kgunda
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=20170718221709.GA18179@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=kgunda@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).