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.3 (#1)
Date: Thu, 02 Feb 2023 16:32:15 +0100 [thread overview]
Message-ID: <87357oaxs0.fsf@BL-laptop> (raw)
Hi,
Here is the first pull request for dt for mvebu for v6.3.
Gregory
The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git tags/mvebu-dt-6.3-1
for you to fetch changes up to 12cb7a3349a53efa8698a01fe0efdc61d887e541:
ARM: dts: dove.dtsi: Move ethphy to fix schema error (2023-01-31 15:38:43 +0100)
----------------------------------------------------------------
mvebu dt for 6.3 (part 1)
Fix errors reported by dtbs_check on dove boards
----------------------------------------------------------------
Michał Grzelak (1):
ARM: dts: dove.dtsi: Move ethphy to fix schema error
arch/arm/boot/dts/dove-cm-a510.dtsi | 14 +++++++++++---
arch/arm/boot/dts/dove-cubox.dts | 15 +++++++++++----
arch/arm/boot/dts/dove.dtsi | 5 -----
3 files changed, 22 insertions(+), 12 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
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.3 (#1)
Date: Thu, 02 Feb 2023 16:32:15 +0100 [thread overview]
Message-ID: <87357oaxs0.fsf@BL-laptop> (raw)
Hi,
Here is the first pull request for dt for mvebu for v6.3.
Gregory
The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git tags/mvebu-dt-6.3-1
for you to fetch changes up to 12cb7a3349a53efa8698a01fe0efdc61d887e541:
ARM: dts: dove.dtsi: Move ethphy to fix schema error (2023-01-31 15:38:43 +0100)
----------------------------------------------------------------
mvebu dt for 6.3 (part 1)
Fix errors reported by dtbs_check on dove boards
----------------------------------------------------------------
Michał Grzelak (1):
ARM: dts: dove.dtsi: Move ethphy to fix schema error
arch/arm/boot/dts/dove-cm-a510.dtsi | 14 +++++++++++---
arch/arm/boot/dts/dove-cubox.dts | 15 +++++++++++----
arch/arm/boot/dts/dove.dtsi | 5 -----
3 files changed, 22 insertions(+), 12 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-02-02 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 15:32 Gregory CLEMENT [this message]
2023-02-02 15:32 ` [GIT PULL] ARM: mvebu: dt for v6.3 (#1) Gregory CLEMENT
2023-02-03 14:30 ` patchwork-bot+linux-soc
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=87357oaxs0.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 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.