From: Judith Mendez <jm@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Andrew Davis <afd@ti.com>, Bryan Brattlof <bb@ti.com>,
Jason Kridner <jkridner@gmail.com>,
Robert Nelson <robertcnelson@gmail.com>
Subject: Re: [PATCH v4 0/3] arm64: dts/bindings: Add support for BeagleBadge
Date: Tue, 26 May 2026 13:11:33 -0500 [thread overview]
Message-ID: <40571850-1292-462f-9bd3-527a810a6730@ti.com> (raw)
In-Reply-To: <20260518124932.plrgsumqgvbij65j@stash>
Hi Nishanth,
On 5/18/26 7:49 AM, Nishanth Menon wrote:
> On 10:35-20260515, Judith Mendez wrote:
>> Hi,
>>
>> BeagleBoard.org BeagleBadge[1] is a compact, affordable open source
>> hardware [2] single board computer based on the Texas Instruments AM62L3
>> SoC designed for IoT and embedded applications. Add base support for
>> the same.
>>
>> SD boot:
>> Link: https://gist.github.com/jmenti/8818fa277597de927dd2b42ab1d2552f
>
> in all patches,
> Is https://www.beagleboard.org/boards/beaglebadge a better canonical
> link?
I can switch links, it seems to be working now.
...
prev parent reply other threads:[~2026-05-26 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 15:35 [PATCH v4 0/3] arm64: dts/bindings: Add support for BeagleBadge Judith Mendez
2026-05-15 15:35 ` [PATCH v4 1/3] dt-bindings: arm: ti: Add am62l3-beaglebadge Judith Mendez
2026-05-15 17:06 ` Conor Dooley
2026-05-15 15:35 ` [PATCH v4 2/3] arm64: dts: ti: Add k3-am62l3-beaglebadge Judith Mendez
2026-05-18 13:11 ` Nishanth Menon
2026-05-26 21:53 ` Judith Mendez
2026-05-26 22:36 ` Judith Mendez
2026-05-15 15:35 ` [PATCH v4 3/3] arm64: defconfig: Enable drivers for BeagleBadge Judith Mendez
2026-05-18 12:49 ` [PATCH v4 0/3] arm64: dts/bindings: Add support " Nishanth Menon
2026-05-26 18:11 ` Judith Mendez [this message]
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=40571850-1292-462f-9bd3-527a810a6730@ti.com \
--to=jm@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jkridner@gmail.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robertcnelson@gmail.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.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