From: Matthias Kaehlcke <mka@chromium.org>
To: Kiran Gunda <kgunda@codeaurora.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
Andy Gross <agross@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
bjorn.andersson@linaro.org, devicetree@vger.kernel.org,
lee.jones@linaro.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
rnayak@codeaurora.org
Subject: Re: [PATCH V2] mfd: qcom-spmi-pmic: Add support for pm6150 and pm6150l
Date: Tue, 21 Jan 2020 11:34:46 -0800 [thread overview]
Message-ID: <20200121193446.GU89495@google.com> (raw)
In-Reply-To: <5dc2f71e.1c69fb81.8912a.f2c0@mx.google.com>
Hi Kiran,
What is the status of this patch? It has outstanding comments and I
couldn't find a later version. Do you plan to post a v3 in the near
future?
Thanks
Matthias
On Wed, Nov 06, 2019 at 08:38:53AM -0800, Stephen Boyd wrote:
> Quoting kgunda@codeaurora.org (2019-11-05 22:43:59)
> > On 2019-11-06 00:49, Stephen Boyd wrote:
> > > Quoting Kiran Gunda (2019-11-04 21:21:49)
> > >> Add the compatibles and PMIC ids for pm6150 and pm6150l PMICs
> > >> found on SC7180 based platforms.
> > >>
> > >> Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>
> > >> ---
> > >> - Changes from V1:
> > >> Sorted the macros and compatibles.
> > >
> > > I don't see anything sorted though.
> > >
> > Sorry .. I might have misunderstood your comment. Let me know if my
> > understanding is correct.
> >
> > >>>> And compatible here.
> > >>> And on macro name here.
> >
> > This means you want to sort all the existing compatible and macros in
> > alpha numeric order ?
>
> Sorry I also got confused on what the driver is doing. I replied on the
> original patch with what is preferred.
>
next prev parent reply other threads:[~2020-01-21 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 5:21 [PATCH V2] mfd: qcom-spmi-pmic: Add support for pm6150 and pm6150l Kiran Gunda
2019-11-05 19:19 ` Stephen Boyd
2019-11-06 6:43 ` kgunda
2019-11-06 16:38 ` Stephen Boyd
2019-11-11 6:15 ` kgunda
2020-01-21 19:34 ` Matthias Kaehlcke [this message]
2020-01-23 5:55 ` kgunda
2019-11-06 16:38 ` Stephen Boyd
2019-11-11 6:14 ` kgunda
2019-11-11 11:28 ` Lee Jones
2019-11-12 9:03 ` 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=20200121193446.GU89495@google.com \
--to=mka@chromium.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kgunda@codeaurora.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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 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.