linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	<arm@kernel.org>,
	soc@kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	<linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] ARM: mvebu: dt for v6.8 (#1)
Date: Wed, 20 Dec 2023 17:52:17 +0100	[thread overview]
Message-ID: <87o7ekbyv2.fsf@BL-laptop> (raw)

Hi,

Here is the first pull request for dt for mvebu for v6.8.

Gregory

The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:

  Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git tags/mvebu-dt-6.8-1

for you to fetch changes up to 62f34e3ec2befcbe5d8a5003f21d53dab80bb03c:

  ARM: dts: marvell: make dts use gpio-fan matrix instead of array (2023-12-15 15:26:41 +0100)

----------------------------------------------------------------
mvebu dt for 6.8 (part 1)

Fix dt for gpio and switch nodes

----------------------------------------------------------------
David Heidelberg (1):
      ARM: dts: marvell: make dts use gpio-fan matrix instead of array

Linus Walleij (1):
      ARM: dts: marvell: Fix some common switch mistakes

 arch/arm/boot/dts/marvell/armada-370-rd.dts        |  26 +++---
 .../dts/marvell/armada-370-seagate-nas-2bay.dts    |   8 +-
 .../dts/marvell/armada-370-seagate-nas-4bay.dts    |   8 +-
 .../dts/marvell/armada-370-synology-ds213j.dts     |  16 ++--
 .../dts/marvell/armada-381-netgear-gs110emx.dts    |  44 +++++----
 .../dts/marvell/armada-385-clearfog-gtr-l8.dts     |  38 ++++----
 .../dts/marvell/armada-385-clearfog-gtr-s4.dts     |  22 ++---
 arch/arm/boot/dts/marvell/armada-385-linksys.dtsi  |  18 ++--
 .../boot/dts/marvell/armada-385-synology-ds116.dts |  16 ++--
 .../boot/dts/marvell/armada-385-turris-omnia.dts   |  20 ++--
 arch/arm/boot/dts/marvell/armada-388-clearfog.dts  |  20 ++--
 arch/arm/boot/dts/marvell/armada-388-gp.dts        |   4 +-
 .../boot/dts/marvell/armada-xp-linksys-mamba.dts   |  18 ++--
 arch/arm/boot/dts/marvell/kirkwood-dnskw.dtsi      |   6 +-
 .../dts/marvell/kirkwood-linkstation-6282.dtsi     |   9 +-
 .../dts/marvell/kirkwood-linkstation-lswxl.dts     |   9 +-
 arch/arm/boot/dts/marvell/kirkwood-lsxl.dtsi       |   9 +-
 arch/arm/boot/dts/marvell/kirkwood-ns2max.dts      |  18 ++--
 arch/arm/boot/dts/marvell/kirkwood-ns2mini.dts     |  18 ++--
 arch/arm/boot/dts/marvell/kirkwood-synology.dtsi   | 102 +++++++++++----------
 .../boot/dts/marvell/mvebu-linkstation-fan.dtsi    |   8 +-
 21 files changed, 217 insertions(+), 220 deletions(-)

-- 
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com

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

                 reply	other threads:[~2023-12-20 16:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87o7ekbyv2.fsf@BL-laptop \
    --to=gregory.clement@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=olof@lixom.net \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=soc@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).