Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Arnd Bergmann" <arnd@kernel.org>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
	dlemoal@kernel.org, linux-rtc@vger.kernel.org,
	neil.armstrong@linaro.org, vkoul@kernel.org,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	olteanv@gmail.com, Frank.Li@kernel.org,
	linux-pci@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
	imx@lists.linux.dev, cassel@kernel.org,
	linux-ide@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 05/13] ARM: orion/dove/mv78xx0: remove all board files
Date: Tue, 08 Sep 2026 16:11:25 +0000	[thread overview]
Message-ID: <20260908161125.E4A331F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260908152808.3928630-6-arnd@kernel.org>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] Orphaned MAINTAINERS entry for the TS-78xx platform.
- [Low] Legacy IRQ, MPP, and GPIO implementations are now unreachable dead code and unnecessarily compiled.
--

commit 67c50c71bc1677d3a7c7538373463163afb7b062
Author: Arnd Bergmann <arnd@arndb.de>
Subject: ARM: orion/dove/mv78xx0: remove all board files

This commit removes the legacy board files for the Orion, Dove, and MV78xx0 
platforms. These files were retained in 2022 due to support in Debian/OpenWRT, 
which is now gone.

> diff --git a/MAINTAINERS b/MAINTAINERS
> index fdd75b73bf293..2bb036e8ddcd9 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3080,8 +3080,6 @@ F:	Documentation/devicetree/bindings/arm/marvell/marvell,orion5x.yaml
>  F:	Documentation/devicetree/bindings/soc/dove/
>  F:	arch/arm/boot/dts/marvell/dove*
>  F:	arch/arm/boot/dts/marvell/orion5x*
> -F:	arch/arm/mach-dove/
> -F:	arch/arm/mach-mv78xx0/
>  F:	arch/arm/mach-orion5x/
>  F:	arch/arm/plat-orion/
>  F:	drivers/bus/mvebu-mbus.c

[Severity: Low]
Since all the board files like arch/arm/mach-orion5x/ts78xx-setup.c are
removed in this patch, should the MAINTAINERS entry for the TS-78xx platform
further down in this file also be removed?

The pattern F: arch/arm/mach-orion5x/ts78xx-* now points to deleted files,
which leaves an orphaned entry for Alexander Clouter.

[ ... ]

> diff --git a/arch/arm/mach-orion5x/Makefile b/arch/arm/mach-orion5x/Makefile
> index 6f54d7fef27a7..7e9634e043185 100644
> --- a/arch/arm/mach-orion5x/Makefile
> +++ b/arch/arm/mach-orion5x/Makefile
> @@ -2,15 +2,6 @@
>  ccflags-y := -I$(srctree)/arch/arm/plat-orion/include
>  
>  obj-y				+= common.o pci.o irq.o mpp.o
> -obj-$(CONFIG_MACH_KUROBOX_PRO)	+= kurobox_pro-setup.o
> -obj-$(CONFIG_MACH_TERASTATION_PRO2)	+= terastation_pro2-setup.o

[Severity: Low]
Are irq.o and mpp.o now completely unreachable code?

Since all the board files that called into these APIs have been removed,
it appears these objects are now unnecessarily compiled into the kernel
image. Should they be removed from obj-y here?

[ ... ]

> diff --git a/arch/arm/plat-orion/Makefile b/arch/arm/plat-orion/Makefile
> index e8c7580df8caf..dfde39cdd992b 100644
> --- a/arch/arm/plat-orion/Makefile
> +++ b/arch/arm/plat-orion/Makefile
> @@ -5,5 +5,5 @@
>  ccflags-y := -I$(src)/include
>  
>  orion-gpio-$(CONFIG_GPIOLIB)      += gpio.o
> -obj-$(CONFIG_PLAT_ORION_LEGACY)   += irq.o pcie.o time.o common.o mpp.o
> +obj-$(CONFIG_PLAT_ORION_LEGACY)   += irq.o pcie.o mpp.o
>  obj-$(CONFIG_PLAT_ORION_LEGACY)   += $(orion-gpio-y)

[Severity: Low]
Similarly, does this leave irq.o, mpp.o, and the orion-gpio-y objects as dead
code as well?

Since their corresponding entry points in the board files were deleted,
could these also be removed from the build?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260908152808.3928630-1-arnd@kernel.org?part=5

  parent reply	other threads:[~2026-09-08 16:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260908152808.3928630-1-arnd@kernel.org>
2026-09-08 15:27 ` [PATCH 05/13] ARM: orion/dove/mv78xx0: remove all board files Arnd Bergmann
2026-09-08 15:34   ` Mark Brown
2026-09-08 16:11   ` sashiko-bot [this message]
2026-09-08 18:21     ` Arnd Bergmann
2026-09-09 12:42       ` [PATCH 05.2/13] ARM: orion5x: fold plat-orion/pcie.c and hw_pci into pci.c Arnd Bergmann
2026-09-08 16:12   ` [PATCH 05/13] ARM: orion/dove/mv78xx0: remove all board files Ulf Hansson
2026-09-08 16:18   ` Andrew Lunn
2026-09-08 16:28   ` Guenter Roeck
2026-09-08 17:33   ` Linus Walleij
2026-09-08 20:14   ` Niklas Cassel
2026-09-09 12:54   ` Gregory CLEMENT
2026-09-11 10:22   ` Daniel Lezcano

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=20260908161125.E4A331F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@kernel.org \
    --cc=cassel@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=imx@lists.linux.dev \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=olteanv@gmail.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@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