From: Marco Felsch <m.felsch@pengutronix.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
Rob Herring <robh@kernel.org>,
Robin van der Gracht <robin@protonic.nl>,
Sascha Hauer <s.hauer@pengutronix.de>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
David Jander <david@protonic.nl>, Shawn Guo <shawnguo@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 3/5] ARM: dts: add Protonic VT7 board
Date: Wed, 22 Apr 2020 09:11:02 +0200 [thread overview]
Message-ID: <20200422071102.ho2zayo23gdkig7r@pengutronix.de> (raw)
In-Reply-To: <20200422070441.5hvozjvcssanqnjb@pengutronix.de>
Hi Oleksij,
On 20-04-22 09:04, Marco Felsch wrote:
> Hi Oleksij,
>
> On 20-04-21 14:40, Oleksij Rempel wrote:
...
> > + reg_1v8: regulator-1v8 {
> > + compatible = "regulator-fixed";
> > + regulator-name = "1v8";
> > + regulator-min-microvolt = <1800000>;
> > + regulator-max-microvolt = <1800000>;
> > + regulator-always-on;
> > + };
Just noticed that this regulator is part of the common .dtsi too,
so we can drop it here.
Regards,
Marco
next prev parent reply other threads:[~2020-04-22 7:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 12:40 [PATCH v6 0/5] mainline Protonic boards Oleksij Rempel
2020-04-21 12:40 ` [PATCH v6 1/5] ARM: dts: add Protonic PRTI6Q board Oleksij Rempel
2020-04-22 7:19 ` Marco Felsch
2020-04-21 12:40 ` [PATCH v6 2/5] ARM: dts: add Protonic WD2 board Oleksij Rempel
2020-04-21 12:40 ` [PATCH v6 3/5] ARM: dts: add Protonic VT7 board Oleksij Rempel
2020-04-22 7:04 ` Marco Felsch
2020-04-22 7:11 ` Marco Felsch [this message]
2020-04-22 9:38 ` David Jander
2020-04-22 11:20 ` Marco Felsch
2020-04-21 12:40 ` [PATCH v6 4/5] ARM: dts: add Protonic RVT board Oleksij Rempel
2020-04-21 12:40 ` [PATCH v6 5/5] dt-bindings: arm: fsl: add different Protonic boards Oleksij Rempel
2020-05-05 19:00 ` Rob Herring
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=20200422071102.ho2zayo23gdkig7r@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=o.rempel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=robin@protonic.nl \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).