From: Robert Nelson <robertcnelson@gmail.com>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Tony Lindgren <tony@atomide.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Andreas Kemnade <andreas@kemnade.info>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Paul Barker <paul.barker@sancloud.com>,
Marc Murphy <marc.murphy@sancloud.com>,
Jason Kridner <jkridner@gmail.com>, Andrew Davis <afd@ti.com>,
Bajjuri Praneeth <praneeth@ti.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 4/7] dt-bindings: omap: Add Seeed BeagleBone Green Eco
Date: Fri, 13 Jun 2025 11:05:24 -0500 [thread overview]
Message-ID: <CAOCHtYg10H537Hu=kMqgFashuNHK_pDFZ_SQsLaJjG-efP9_Rg@mail.gmail.com> (raw)
In-Reply-To: <20250613-bbg-v3-4-514cdc768448@bootlin.com>
On Fri, Jun 13, 2025 at 10:51 AM Kory Maincent
<kory.maincent@bootlin.com> wrote:
>
> Document the seed,am335x-bone-green-eco compatible string in the
> appropriate place within the omap family binding file.
just a small miss (missing e): `seeed,am335x-bone-green-eco`
Regards,
--
Robert Nelson
https://rcn-ee.com/
next prev parent reply other threads:[~2025-06-13 16:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 15:49 [PATCH v3 0/7] Add support for BeagleBone Green Eco board Kory Maincent
2025-06-13 15:49 ` [PATCH v3 1/7] dt-bindings: omap: Add missing AM33xx compatible strings Kory Maincent
2025-06-13 17:10 ` Andrew Davis
2025-06-13 17:21 ` Kory Maincent
2025-06-13 15:49 ` [PATCH v3 2/7] ARM: dts: omap: Remove incorrect compatible strings from device trees Kory Maincent
2025-06-13 20:33 ` Jason Kridner
[not found] ` <CA+T6QPnaCFZyRsv9q3bcOrTc22nA0AOXy0tR_SpAkGVVPQqfLg@mail.gmail.com>
2025-06-16 8:39 ` Kory Maincent
2025-06-16 11:39 ` Josua Mayer
2025-06-16 12:29 ` Kory Maincent
2025-06-13 15:49 ` [PATCH v3 3/7] arm: dts: omap: am335x-bone-common: Rename tps to generic pmic node Kory Maincent
2025-06-13 15:49 ` [PATCH v3 4/7] dt-bindings: omap: Add Seeed BeagleBone Green Eco Kory Maincent
2025-06-13 16:05 ` Robert Nelson [this message]
2025-06-16 14:52 ` Conor Dooley
2025-06-13 15:49 ` [PATCH v3 5/7] arm: dts: omap: Add support for BeagleBone Green Eco board Kory Maincent
2025-06-13 16:03 ` Robert Nelson
2025-06-13 16:15 ` Kory Maincent
2025-06-13 15:49 ` [PATCH v3 6/7] arm: omap2plus_defconfig: Enable TPS65219 regulator Kory Maincent
2025-06-13 15:49 ` [PATCH v3 7/7] arm: multi_v7_defconfig: " Kory Maincent
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='CAOCHtYg10H537Hu=kMqgFashuNHK_pDFZ_SQsLaJjG-efP9_Rg@mail.gmail.com' \
--to=robertcnelson@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=afd@ti.com \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jkridner@gmail.com \
--cc=khilman@baylibre.com \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marc.murphy@sancloud.com \
--cc=paul.barker@sancloud.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).