Am Dienstag, 7. Juli 2026, 18:09:15 Mitteleuropäische Sommerzeit schrieb 
Quentin Schulz:
> The ARM ROCKCHIP entry already specifies an N: rockchip so we don't need
> to repeat a path with F: if it has rockchip in the path, so drop it.
> 
> Note that for some reason get_maintainer.pl doesn't return the exact
> same list before and after this patch.
> 
> Signed-off-by: Quentin Schulz <[email protected]>
> ---
>  MAINTAINERS | 15 +--------------
>  1 file changed, 1 insertion(+), 14 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 45e9076de671..e2c78ce39161 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -574,12 +574,10 @@ M:      Philipp Tomsich <[email protected]>
>  M:   Kever Yang <[email protected]>
>  S:   Maintained
>  T:   git https://source.denx.de/u-boot/custodians/u-boot-rockchip.git
> +N:   rockchip

It took me a while to realize the existing N was at the end, so gets
moved up here :-)

Reviewed-by: Heiko Stuebner <[email protected]>


>  F:   arch/arm/dts/px30*
>  F:   arch/arm/dts/rk3*
> -F:   arch/arm/dts/rockchip*
>  F:   arch/arm/dts/rv11*
> -F:   arch/arm/include/asm/arch-rockchip/
> -F:   arch/arm/mach-rockchip/
>  F:   board/amarula/vyasa-rk3288/
>  F:   board/anbernic/rgxx3_rk3566/
>  F:   board/armsom/sige7-rk3588/
> @@ -590,25 +588,14 @@ F:      board/mqmaker/miqi_rk3288/
>  F:   board/phytec/phycore_rk3288
>  F:   board/pine64
>  F:   board/radxa/
> -F:   board/rockchip/
>  F:   board/theobroma-systems
>  F:   board/vamrs/rock960_rk3399/
> -F:   drivers/clk/rockchip/
>  F:   drivers/gpio/rk_gpio.c
> -F:   drivers/misc/rockchip-efuse.c
> -F:   drivers/mmc/rockchip_sdhci.c
> -F:   drivers/mmc/rockchip_dw_mmc.c
> -F:   drivers/pinctrl/rockchip/
> -F:   drivers/ram/rockchip/
> -F:   drivers/sysreset/sysreset_rockchip.c
> -F:   drivers/ufs/*rockchip*
> -F:   drivers/video/rockchip/
>  F:   tools/rkcommon.c
>  F:   tools/rkcommon.h
>  F:   tools/rkimage.c
>  F:   tools/rksd.c
>  F:   tools/rkspi.c
> -N:   rockchip
>  
>  ARM SAMSUNG
>  M:   Minkyu Kang <[email protected]>
> 
> 




Reply via email to