linux-kernel - Re: [PATCH] mips: lantiq: danube: add missing device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aLF_rGqmA0VMEiyx@alpha.franken.de>
Date: Fri, 29 Aug 2025 12:23:40 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Aleksander Jan Bajkowski <olek2@...pl>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
	devicetree@...r.kernel.org, linux-mips@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mips: lantiq: danube: add missing device_type in pci node

On Mon, Aug 11, 2025 at 03:34:13PM +0200, Aleksander Jan Bajkowski wrote:
> This fixes the following warning:
> arch/mips/boot/dts/lantiq/danube_easy50712.dtb: pci@...5400 (lantiq,pci-xway): 'device_type' is a required property
> 	from schema $id: http://devicetree.org/schemas/pci/pci-bus-common.yaml#
> 
> Signed-off-by: Aleksander Jan Bajkowski <olek2@...pl>
> ---
>  arch/mips/boot/dts/lantiq/danube.dtsi | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/mips/boot/dts/lantiq/danube.dtsi b/arch/mips/boot/dts/lantiq/danube.dtsi
> index 7a7ba66aa534..9cba16dd5dae 100644
> --- a/arch/mips/boot/dts/lantiq/danube.dtsi
> +++ b/arch/mips/boot/dts/lantiq/danube.dtsi
> @@ -100,6 +100,8 @@ pci0: pci@...5400 {
>  				  0x1000000 0 0x00000000 0xae00000 0 0x200000>; /* io space */
>  			reg = <0x7000000 0x8000		/* config space */
>  				0xe105400 0x400>;	/* pci bridge */
> +
> +			device_type = "pci";
>  		};
>  	};
>  };
> -- 
> 2.47.2

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]