linux-kernel - Re: [PATCH v3 2/7] ARM: dts: omap: Remove incorrect compatible strings from device trees

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: <20250616142913.1afad458@kmaincent-XPS-13-7390>
Date: Mon, 16 Jun 2025 14:29:13 +0200
From: Kory Maincent <kory.maincent@...tlin.com>
To: Josua Mayer <josua.mayer@....eu>
Cc: Jason Kridner <jkridner@...il.com>, Tony Lindgren <tony@...mide.com>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Aaro Koskinen <aaro.koskinen@....fi>,
 Andreas Kemnade <andreas@...nade.info>, Kevin Hilman
 <khilman@...libre.com>, Roger Quadros <rogerq@...nel.org>, Russell King
 <linux@...linux.org.uk>, Paul Barker <paul.barker@...cloud.com>, Marc
 Murphy <marc.murphy@...cloud.com>, Andrew Davis <afd@...com>, Bajjuri
 Praneeth <praneeth@...com>, Liam Girdwood <lgirdwood@...il.com>, Mark Brown
 <broonie@...nel.org>, Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
 linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 2/7] ARM: dts: omap: Remove incorrect compatible
 strings from device trees

Le Mon, 16 Jun 2025 14:39:03 +0300,
Josua Mayer <josua.mayer@....eu> a écrit :

> Hi Kory,
> 
> Am 16.06.25 um 11:39 schrieb Kory Maincent:
> > Le Fri, 13 Jun 2025 13:52:23 -0500,
> > Jason Kridner <jkridner@...il.com> a écrit :
> >  
> >> On Fri, Jun 13, 2025 at 10:49 AM Kory Maincent <kory.maincent@...tlin.com>
> >> wrote:
> >>  
>  [...]  
> >>
> >> We have software that looks at these in running systems, so I’d be ok not
> >> to change. If changing, why not “BeagleBoard.org BeagleBone”? Not sure of
> >> the convention to mention the SoC, but AM335x is not part of the product
> >> name.  
> > Is it ok to change it or not then? Ok to move on to BeagleBoard.org.  
> The Debian project most notably uses the "model" string:
> 
> https://salsa.debian.org/installer-team/flash-kernel/-/blob/master/db/all.db?ref_type=heads#L2191
> 
> When that changes inside a dtb by kernel update, users may be unable to 
> boot.
> Therefore I would recommend against changing "model" values.

Maybe they will have to follow the change.
Don't know if this should not be changed over time even if they are wrong from
the beginning.

It would be nice to have a devicetree maintainer's opinion on this but I don't
think they will reach this message.

I think I will keep old model values for this series then, I don't want to
block this series on this topic.

Regards,
-- 
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com