ARM: mvebu: fixes for v7.0 (#1)
Hi,
Here is the first pull request for fixes for mvebu for v7.0.
Gregory
The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git tags/mvebu-fixes-7.0-1
for you to fetch changes up to edb7efa767da8bb82d724b85178be251ec4e060e:
dt-bindings: arm64: add Marvell 7k COMe boards (2026-03-13 16:41:11 +0100)
----------------------------------------------------------------
mvebu fixes for 7.0 (part 1)
- Add bindings to validate the device tree that has already been merged.
----------------------------------------------------------------
Elad Nachman (1):
dt-bindings: arm64: add Marvell 7k COMe boards
.../devicetree/bindings/arm/marvell/armada-7k-8k.yaml | 11 +++++++++++ 1 file changed, 11 insertions(+)
Signature · 3 lines
Grégory CLEMENT, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Quoted 14 lines · Gregory CLEMENT
Hi,
Here is the first pull request for fixes for mvebu for v7.0.
Gregory
The following changes since commit
6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.gittags/mvebu-fixes-7.0-1
Quoted 8 lines
for you to fetch changes up to
edb7efa767da8bb82d724b85178be251ec4e060e:dt-bindings: arm64: add Marvell 7k COMe boards (2026-03-13 16:41:11 +0100)
----------------------------------------------------------------
mvebu fixes for 7.0 (part 1)- Add bindings to validate the device tree that has already been merged.
Merged when? Why is this a fix not a development (e.g. documenting something 10 years old)?
Please write informative pull requests. You want to here provide the context WHY maintainer should take this as fixes.
Best regards,
Krzysztof
Hello Krzysztof,
Quoted 22 lines · Gregory CLEMENT
Quoted 21 lines
Hi,
Here is the first pull request for fixes for mvebu for v7.0.
Gregory
The following changes since commit
6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.gittags/mvebu-fixes-7.0-1for you to fetch changes up to
edb7efa767da8bb82d724b85178be251ec4e060e:dt-bindings: arm64: add Marvell 7k COMe boards (2026-03-13 16:41:11 +0100)
----------------------------------------------------------------
mvebu fixes for 7.0 (part 1)
Quoted 7 lines
Quoted 1 line
- Add bindings to validate the device tree that has already been merged.
Merged when? Why is this a fix not a development (e.g. documenting something 10 years old)?
Please write informative pull requests. You want to here provide the context WHY maintainer should take this as fixes.
Okay, I will add a reference to the thread and a summary. In short, a new device tree has been merged without the binding, which caused warnings when running dtbs_checks and annoyed Rob.
Regards,
Gregory
Quoted 4 lines
Best regards,
Krzysztof
Signature · 3 lines
Grégory CLEMENT, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Quoted 14 lines · Gregory CLEMENT
Hi,
Here is the first pull request for fixes for mvebu for v7.0.
Gregory
The following changes since commit
6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.gittags/mvebu-fixes-7.0-1
Quoted 8 lines
for you to fetch changes up to
edb7efa767da8bb82d724b85178be251ec4e060e:dt-bindings: arm64: add Marvell 7k COMe boards (2026-03-13 16:41:11 +0100)
----------------------------------------------------------------
mvebu fixes for 7.0 (part 1)- Add bindings to validate the device tree that has already been merged.
This has 0 days in next:
Days in linux-next:
----------------------------------------
0 | + (1)
Commits with 0 days in linux-next (1 of 1: 100.0%):
So it will wait. Please send pull requests with code which was in the next for minimum one next release for fixes and few (5-10) for development.
Best regards,
Krzysztof