All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	heiko.thiery@gmail.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Subject: Re: [PATCH v2 1/2] arm64: dts: imx8mn-evk: use proper names for PMIC outputs
Date: Wed, 6 Apr 2022 21:20:56 +0800	[thread overview]
Message-ID: <20220406132056.GR129381@dragon> (raw)
In-Reply-To: <20220224103030.2040048-1-michael@walle.cc>

On Thu, Feb 24, 2022 at 11:30:29AM +0100, Michael Walle wrote:
> Use the power signal names as given in the schematics of the reference
> board.
> 
> Signed-off-by: Michael Walle <michael@walle.cc>

Applied both, thanks!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	heiko.thiery@gmail.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Subject: Re: [PATCH v2 1/2] arm64: dts: imx8mn-evk: use proper names for PMIC outputs
Date: Wed, 6 Apr 2022 21:20:56 +0800	[thread overview]
Message-ID: <20220406132056.GR129381@dragon> (raw)
In-Reply-To: <20220224103030.2040048-1-michael@walle.cc>

On Thu, Feb 24, 2022 at 11:30:29AM +0100, Michael Walle wrote:
> Use the power signal names as given in the schematics of the reference
> board.
> 
> Signed-off-by: Michael Walle <michael@walle.cc>

Applied both, thanks!

  parent reply	other threads:[~2022-04-06 13:22 UTC|newest]

Thread overview: 14+ 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 ` 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 10:30   ` Michael Walle
2022-02-24 12:09   ` Heiko Thiery
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-24 12:10   ` Heiko Thiery
2022-02-26 12:58 ` Fabio Estevam
2022-02-26 12:58   ` Fabio Estevam
2022-03-14  7:30 ` Michael Walle
2022-03-14  7:30   ` Michael Walle
2022-04-06 13:20 ` Shawn Guo [this message]
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=20220406132056.GR129381@dragon \
    --to=shawnguo@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --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 \
    /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.