From: Stefan Wahren <stefan.wahren@i2se.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
Mark Rutland <mark.rutland@arm.com>,
NXP Linux Team <linux-imx@nxp.com>,
Anson Huang <Anson.Huang@nxp.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 0/2] regulator: pfuze100: add pfuze3001 support
Date: Sat, 16 Jun 2018 21:25:21 +0200 (CEST) [thread overview]
Message-ID: <2103480434.399682.1529177121085@email.1und1.de> (raw)
In-Reply-To: <CAOMZO5D7FAiE8dXKmLHCmOdHek4w_LuYjz8uP9jdD7U6Z-7f5Q@mail.gmail.com>
Hi Fabio,
> Fabio Estevam <festevam@gmail.com> hat am 16. Juni 2018 um 20:40 geschrieben:
>
>
> Hi Stefan,
>
> On Fri, Jun 15, 2018 at 8:44 AM, Stefan Wahren <stefan.wahren@i2se.com> wrote:
> > This patch series adds support for the NXP PMIC PF3001. This
> > based mostly on the patches by Robin Gong and Mauro Salvini from
> > here [1].
> >
> > [1] - https://community.nxp.com/docs/DOC-331899
> >
> > Stefan Wahren (2):
> > dt-bindings: pfuze100: add pfuze3001 support
> > regulator: pfuze100: add pfuze3001 support
>
> This series looks good.
>
> Any particular reason for marking it as RFC?
since most of the changes based on Robin's and Mauro's work.
>
> Thanks
prev parent reply other threads:[~2018-06-16 19:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 11:44 Stefan Wahren
2018-06-15 11:44 ` [PATCH RFC 1/2] dt-bindings: " Stefan Wahren
2018-06-18 12:01 ` Applied "regulator: pfuze100: add pfuze3001 support" to the regulator tree Mark Brown
2018-06-15 11:44 ` [PATCH RFC 2/2] regulator: pfuze100: add pfuze3001 support Stefan Wahren
2018-06-18 12:01 ` Applied "regulator: pfuze100: add pfuze3001 support" to the regulator tree Mark Brown
2018-06-16 18:40 ` [PATCH RFC 0/2] regulator: pfuze100: add pfuze3001 support Fabio Estevam
2018-06-16 19:25 ` Stefan Wahren [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=2103480434.399682.1529177121085@email.1und1.de \
--to=stefan.wahren@i2se.com \
--cc=Anson.Huang@nxp.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®