From: Kory Maincent <kory.maincent@bootlin.com>
To: Conor Dooley <conor@kernel.org>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Andreas Kemnade <andreas@kemnade.info>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Barker <paul.barker@sancloud.com>,
Marc Murphy <marc.murphy@sancloud.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Romain Gantois <romain.gantois@bootlin.com>,
Thomas Bonnefille <thomas.bonnefille@bootlin.com>,
Bajjuri Praneeth <praneeth@ti.com>, Andrew Davis <afd@ti.com>
Subject: Re: [PATCH 1/2] dt-bindings: omap: Add missing AM33xx compatible strings
Date: Fri, 20 Jun 2025 16:26:17 +0200 [thread overview]
Message-ID: <20250620162617.50ca0a7f@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <20250620-widow-licorice-66fbd43b18b0@spud>
Le Fri, 20 Jun 2025 15:09:41 +0100,
Conor Dooley <conor@kernel.org> a écrit :
> On Fri, Jun 20, 2025 at 03:08:24PM +0100, Conor Dooley wrote:
> > On Fri, Jun 20, 2025 at 10:24:08AM +0200, Kory Maincent wrote:
> > > Add several compatible strings that were missing from the binding
> > > documentation for AM33xx-based boards. Update vendor prefix from
> > > "ti" to "beagle" for BeagleBone to match actual hardware vendors.
> > >
> > > Reviewed-by: Andrew Davis <afd@ti.com>
> > > Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> >
> > This is a v1 apparently, what is the relationship between this patch and
> > https://lore.kernel.org/all/20250617-bbg-v4-1-827cbd606db6@bootlin.com/
> > ?
>
> (I ask because at a scan I didn't see differences and I had acked the
> last one, which doesn't show here even though Andrew's r-b does)
Oh, you acked-by was lost in the void during the patch series split sorry for
that.
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-06-20 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 8:24 [PATCH 0/2] arm: dts: OMAP: Clean up devicetree bindings and compatible strings Kory Maincent
2025-06-20 8:24 ` [PATCH 1/2] dt-bindings: omap: Add missing AM33xx " Kory Maincent
2025-06-20 14:08 ` Conor Dooley
2025-06-20 14:09 ` Conor Dooley
2025-06-20 14:26 ` Kory Maincent [this message]
2025-06-23 14:36 ` Conor Dooley
2025-06-20 8:24 ` [PATCH 2/2] arm: dts: omap: Remove incorrect compatible strings from device trees Kory Maincent
2025-06-20 14:15 ` [PATCH 0/2] arm: dts: OMAP: Clean up devicetree bindings and compatible strings Conor Dooley
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=20250620162617.50ca0a7f@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=aaro.koskinen@iki.fi \
--cc=afd@ti.com \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=marc.murphy@sancloud.com \
--cc=paul.barker@sancloud.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=romain.gantois@bootlin.com \
--cc=thomas.bonnefille@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tony@atomide.com \
/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