[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250610-during-unstirred-9e5b3de34467@spud>
Date: Tue, 10 Jun 2025 16:29:26 +0100
From: Conor Dooley <conor@...nel.org>
To: Andreas Kemnade <andreas@...nade.info>
Cc: Kory Maincent <kory.maincent@...tlin.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>,
Kevin Hilman <khilman@...libre.com>,
Roger Quadros <rogerq@...nel.org>,
Russell King <linux@...linux.org.uk>,
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 v2 2/5] binding: omap: Add lots of missing omap AM33
compatibles
On Mon, Jun 09, 2025 at 09:50:44PM +0200, Andreas Kemnade wrote:
> Am Mon, 9 Jun 2025 18:03:05 +0100
> schrieb Conor Dooley <conor@...nel.org>:
>
> > > + - description: TI bone variants based on TI AM335
> >
> > "bone variant" sounds like some shortand or nickname. Are the boards not
> > called "beaglebone green" and "beaglebone black"? Whatever about the
> > compatible, the description should use the full name I think.
> >
> we have an enum below it listing all those variants. So "variants"
> makes sense here, but better "TI Beaglebone variants"
Yes, this was a comment on calling it a "bone", when that's not what the
boards are called in their marketing material etc, not objecting to the
word variant.
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists