devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Michael Walle <michael@walle.cc>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	Heiko Thiery <heiko.thiery@gmail.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH v2 1/2] arm64: dts: imx8mn-evk: use proper names for PMIC outputs
Date: Sat, 26 Feb 2022 09:58:47 -0300	[thread overview]
Message-ID: <CAOMZO5A2WeSB4GWZTqxT4mHjvVs2jgjUnZM-K2cPy3SBic-L2g@mail.gmail.com> (raw)
In-Reply-To: <20220224103030.2040048-1-michael@walle.cc>

Hi Michael,

On Thu, Feb 24, 2022 at 7:30 AM Michael Walle <michael@walle.cc> wrote:
>
> Use the power signal names as given in the schematics of the reference
> board.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> Changes since v1:
>  - swap buck1 and buck2

Reviewed-by: Fabio Estevam <festevam@gmail.com>

  parent reply	other threads:[~2022-02-26 12:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 10:30 [PATCH v2 1/2] arm64: dts: imx8mn-evk: use proper names for PMIC outputs Michael Walle
2022-02-24 10:30 ` [PATCH v2 2/2] arm64: dts: imx8mn-evk: fix the min/max voltages of the PMIC Michael Walle
2022-02-24 12:09   ` Heiko Thiery
2022-02-24 12:10 ` [PATCH v2 1/2] arm64: dts: imx8mn-evk: use proper names for PMIC outputs Heiko Thiery
2022-02-26 12:58 ` Fabio Estevam [this message]
2022-03-14  7:30 ` Michael Walle
2022-04-06 13:20 ` Shawn Guo

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=CAOMZO5A2WeSB4GWZTqxT4mHjvVs2jgjUnZM-K2cPy3SBic-L2g@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko.thiery@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=robh+dt@kernel.org \
    --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).