From: Mark Brown <broonie@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Adrien Grassein <adrien.grassein@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>,
Troy Kisky <troy.kisky@boundarydevices.com>,
Gary Bisson <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:24:00 +0000 [thread overview]
Message-ID: <20201215132400.GE4738@sirena.org.uk> (raw)
In-Reply-To: <CAOMZO5A_Gtwn=AFwJXf_wpC4k902Hg=tCMWpcFUGNWOg9me6_w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
On Tue, Dec 15, 2020 at 10:20:02AM -0300, Fabio Estevam wrote:
> On Tue, Dec 15, 2020 at 10:16 AM Adrien Grassein
> <adrien.grassein@gmail.com> wrote:
> > Could you please tell me where this driver was merged?
> > I checked the main kernel Linux and I can find out this one.
> It is in the linux-next tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers?h=next-20201215&id=d3795d6321ecaa55d94dc24c3b1e3cce608aabd6
Coming to there from my for-next branch - it's also already been sent in
a pull request to Linus so will hopefully be hitting his tree soonish.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-12-15 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 22:58 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 [this message]
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=20201215132400.GE4738@sirena.org.uk \
--to=broonie@kernel.org \
--cc=adrien.grassein@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome