From: Jagan Teki <jagan@amarulasolutions.com>
To: Mark Brown <broonie@kernel.org>,
Adrien Grassein <adrien.grassein@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Troy Kisky <troy.kisky@boundarydevices.com>,
Gary Bisson <gary.bisson@boundarydevices.com>
Subject: Re: [PATCH v3 0/2] Add support of nxp pf8x00 regulator
Date: Wed, 16 Dec 2020 01:47:32 +0530 [thread overview]
Message-ID: <CAMty3ZB1SPVwU_GA8PCYgrrPExLfjj+koij45evzef5BYQrAmw@mail.gmail.com> (raw)
In-Reply-To: <20201215130622.GD4738@sirena.org.uk>
On Tue, Dec 15, 2020 at 6:36 PM Mark Brown <broonie@kernel.org> wrote:
>
> On Mon, Dec 14, 2020 at 11:58:49PM +0100, Adrien Grassein wrote:
>
> > this set of patch intends to add the support of the pf8x00 PMIC
> > regulators. This family of PMIC contains 12 regulators (7 bucks
> > converters, 4 LDO, 1 RTC supply). All these 12 regulators are
> > configurable via an OTP memory and by i2c at runtime for some
> > specific properties.
>
> This looks to have raced with the addition of support for the same
> device by Jagan Teki - unfortunately I didn't register that I'd seen
> other patches for the same driver go past so I applied Jagan's version
> (both look to be based on original work by Troy), sorry about that.
> Could you please take a look at what got merged and send incremental
> improvements on top of it - I do notice that I missed the use of the
> wildcard compatible in there so that needs fixing at least. :/
Sorry, I'm unable to understand the pharse here. is there any issue
with the existing patchset?
Thanks,
Jagan.
prev parent reply other threads:[~2020-12-15 20:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 22:58 [PATCH v3 0/2] Add support of nxp pf8x00 regulator Adrien Grassein
2020-12-14 22:58 ` [PATCH v3 1/2] dt-bindings: regulator: add pf8x00 PMIC Adrien Grassein
2020-12-15 14:26 ` Rob Herring
2020-12-15 15:00 ` Rob Herring
2020-12-14 22:58 ` [PATCH v3 2/2] regulator: pf8x00: add support of nxp pf8x00 regulator Adrien Grassein
2020-12-15 13:06 ` [PATCH v3 0/2] Add " Mark Brown
2020-12-15 13:14 ` Adrien Grassein
2020-12-15 13:20 ` Fabio Estevam
2020-12-15 13:24 ` Mark Brown
2020-12-15 13:33 ` Adrien Grassein
2020-12-15 20:17 ` Jagan Teki [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=CAMty3ZB1SPVwU_GA8PCYgrrPExLfjj+koij45evzef5BYQrAmw@mail.gmail.com \
--to=jagan@amarulasolutions.com \
--cc=adrien.grassein@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gary.bisson@boundarydevices.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=troy.kisky@boundarydevices.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).