From: Mark Brown <broonie@kernel.org>
To: Adrien Grassein <adrien.grassein@gmail.com>
Cc: lgirdwood@gmail.com, robh+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
troy.kisky@boundarydevices.com, gary.bisson@boundarydevices.com,
Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [PATCH v3 0/2] Add support of nxp pf8x00 regulator
Date: Tue, 15 Dec 2020 13:06:22 +0000 [thread overview]
Message-ID: <20201215130622.GD4738@sirena.org.uk> (raw)
In-Reply-To: <20201214225851.23342-1-adrien.grassein@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
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. :/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-12-15 13:07 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 ` Mark Brown [this message]
2020-12-15 13:14 ` [PATCH v3 0/2] Add " 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
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=20201215130622.GD4738@sirena.org.uk \
--to=broonie@kernel.org \
--cc=adrien.grassein@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=gary.bisson@boundarydevices.com \
--cc=jagan@amarulasolutions.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 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.