From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Gary Bisson <bisson.gary@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sean Wang <sean.wang@mediatek.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v4 1/4] dt-bindings: vendor-prefixes: Add Ezurio LLC
Date: Wed, 3 Dec 2025 07:55:53 +0100 [thread overview]
Message-ID: <81ea7372-9172-4ee5-9a90-66cf06c40062@collabora.com> (raw)
In-Reply-To: <20251202-review-v4-1-93f5cd2a0d4a@gmail.com>
Il 02/12/25 23:08, Gary Bisson ha scritto:
> Ezurio is the new name of Laird Connectivity after it acquired Boundary
> Devices.
>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Signed-off-by: Gary Bisson <bisson.gary@gmail.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2025-12-03 6:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 22:08 [PATCH v4 0/4] Add support for Ezurio MediaTek platforms Gary Bisson
2025-12-02 22:08 ` [PATCH v4 1/4] dt-bindings: vendor-prefixes: Add Ezurio LLC Gary Bisson
2025-12-03 6:55 ` AngeloGioacchino Del Regno [this message]
2025-12-02 22:08 ` [PATCH v4 2/4] dt-bindings: arm: mediatek: Add Ezurio Tungsten entries Gary Bisson
2025-12-03 6:55 ` AngeloGioacchino Del Regno
2025-12-03 7:49 ` Krzysztof Kozlowski
2025-12-02 22:08 ` [PATCH v4 3/4] arm64: dts: mediatek: add device tree for Tungsten 510 board Gary Bisson
2025-12-03 6:50 ` AngeloGioacchino Del Regno
2025-12-03 6:54 ` AngeloGioacchino Del Regno
2025-12-03 10:48 ` Gary Bisson
2025-12-02 22:08 ` [PATCH v4 4/4] arm64: dts: mediatek: add device tree for Tungsten 700 board Gary Bisson
2025-12-03 6:54 ` AngeloGioacchino Del Regno
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=81ea7372-9172-4ee5-9a90-66cf06c40062@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=bisson.gary@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=sean.wang@mediatek.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