linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Benjamin Fair <benjaminfair@google.com>,
	Joel Stanley <joel@jms.id.au>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Tony Lindgren <tony@atomide.com>,
	Patrick Venture <venture@google.com>,
	Tali Perry <tali.perry1@gmail.com>, Nancy Yuen <yuenn@google.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Magnus Damm <magnus.damm@gmail.com>,
	Gregory Clement <gregory.clement@bootlin.com>,
	Avi Fishman <avifishman70@gmail.com>,
	Li Yang <leoyang.li@nxp.com>,
	Russell King <linux@armlinux.org.uk>,
	Andrew Jeffery <andrew@aj.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Dinh Nguyen <dinguyen@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	UNGLinuxDriver@microchip.com,
	Benoît Cousson <bcousson@baylibre.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Stefan Agner <stefan@agner.ch>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Andrew Lunn  <andrew@lunn.ch>, Tomer Maimon <tmaimon77@gmail.com>,
	Sascha Hauer <s.hauer@pengutronix.de>
Cc: devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	openbmc@lists.ozlabs.org, linux-aspeed@lists.ozlabs.org,
	linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	Rob Herring <robh+dt@kernel.org>,
	linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: (subset) [PATCH 00/11] Fix pca954x i2c-mux node names
Date: Thu, 08 Dec 2022 23:40:16 +1100	[thread overview]
Message-ID: <167050321678.1457988.4158904572849937193.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <cover.1669999298.git.geert+renesas@glider.be>

On Fri, 2 Dec 2022 17:49:15 +0100, Geert Uytterhoeven wrote:
> 	Hi all,
> 
> According to the I2C bus multiplexer/switch DT bindings, i2c-mux nodes
> should be named "i2c-mux" (or something similar).
> This patch series renames nodes for pca954x i2c-muxes that are flagged
> by
> 
> [...]

Applied to powerpc/next.

[11/11] powerpc: dts: fsl: Fix pca954x i2c-mux node names
        https://git.kernel.org/powerpc/c/3ae7c96dd51025550c8001c6f833337f11d00807

cheers

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

      parent reply	other threads:[~2022-12-08 12:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 16:49 [PATCH 00/11] Fix pca954x i2c-mux node names Geert Uytterhoeven
2022-12-02 16:49 ` [PATCH 01/11] ARM: dts: ti: " Geert Uytterhoeven
2023-01-19  8:18   ` Tony Lindgren
2022-12-02 16:49 ` [PATCH 02/11] ARM: dts: aspeed: " Geert Uytterhoeven
2022-12-02 16:49 ` [PATCH 03/11] ARM: dts: imx: Fix pca9547 i2c-mux node name Geert Uytterhoeven
2022-12-31 12:39   ` Shawn Guo
2022-12-02 16:49 ` [PATCH 04/11] ARM: dts: nuvoton: Fix pca954x i2c-mux node names Geert Uytterhoeven
2022-12-02 16:49 ` [PATCH 05/11] ARM: dts: socfpga: Fix pca9548 i2c-mux node name Geert Uytterhoeven
2022-12-06 21:01   ` Dinh Nguyen
2022-12-02 16:49 ` [PATCH 06/11] ARM: dts: vf610: Fix pca9548 i2c-mux node names Geert Uytterhoeven
2022-12-31 12:39   ` Shawn Guo
2022-12-02 16:49 ` [PATCH 07/11] arm64: dts: freescale: Fix pca954x " Geert Uytterhoeven
2022-12-31 12:40   ` Shawn Guo
2022-12-02 16:49 ` [PATCH 08/11] arm64: dts: marvell: " Geert Uytterhoeven
2022-12-02 16:49 ` [PATCH 09/11] arm64: dts: renesas: ulcb-kf: Fix pca9548 " Geert Uytterhoeven
2022-12-02 16:49 ` [PATCH 10/11] MIPS: mscc: jaguar2: Fix pca9545 " Geert Uytterhoeven
2022-12-08 10:36   ` Thomas Bogendoerfer
2022-12-02 16:49 ` [PATCH 11/11] powerpc: dts: fsl: Fix pca954x " Geert Uytterhoeven
2022-12-03 13:09 ` [PATCH 00/11] " Philippe Mathieu-Daudé
2022-12-08 12:40 ` Michael Ellerman [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=167050321678.1457988.4158904572849937193.b4-ty@ellerman.id.au \
    --to=patch-notifications@ellerman.id.au \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@aj.id.au \
    --cc=andrew@lunn.ch \
    --cc=avifishman70@gmail.com \
    --cc=bcousson@baylibre.com \
    --cc=benjaminfair@google.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=gregory.clement@bootlin.com \
    --cc=joel@jms.id.au \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=magnus.damm@gmail.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    --cc=tali.perry1@gmail.com \
    --cc=tmaimon77@gmail.com \
    --cc=tony@atomide.com \
    --cc=tsbogend@alpha.franken.de \
    --cc=venture@google.com \
    --cc=yuenn@google.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;
as well as URLs for NNTP newsgroup(s).