From: Conor Dooley <conor@kernel.org>
To: Patrick Barsanti <patrick.barsanti@amarulasolutions.com>
Cc: devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, heiko@sntech.de, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-amarula@amarulasolutions.com, michael@amarulasolutions.com,
dario.binacchi@amarulasolutions.com
Subject: Re: [PATCH 1/3] dt-bindings: vendor-prefixes: Add Axelera AI
Date: Mon, 25 May 2026 17:43:39 +0100 [thread overview]
Message-ID: <20260525-prototype-dingbat-1aa80f9a112e@spud> (raw)
In-Reply-To: <20260522174918.61523-2-patrick.barsanti@amarulasolutions.com>
[-- Attachment #1.1: Type: text/plain, Size: 109 bytes --]
With the changed company name
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: changes-requested
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Patrick Barsanti <patrick.barsanti@amarulasolutions.com>
Cc: devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, heiko@sntech.de, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-amarula@amarulasolutions.com, michael@amarulasolutions.com,
dario.binacchi@amarulasolutions.com
Subject: Re: [PATCH 1/3] dt-bindings: vendor-prefixes: Add Axelera AI
Date: Mon, 25 May 2026 17:43:39 +0100 [thread overview]
Message-ID: <20260525-prototype-dingbat-1aa80f9a112e@spud> (raw)
In-Reply-To: <20260522174918.61523-2-patrick.barsanti@amarulasolutions.com>
[-- Attachment #1: Type: text/plain, Size: 109 bytes --]
With the changed company name
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: changes-requested
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-05-25 16:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 17:49 [PATCH 0/3] arm64: dts: rockchip: Add support for Axelera Metis SBC Patrick Barsanti
2026-05-22 17:49 ` Patrick Barsanti
2026-05-22 17:49 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Axelera AI Patrick Barsanti
2026-05-22 17:49 ` Patrick Barsanti
2026-05-22 18:12 ` Heiko Stuebner
2026-05-22 18:12 ` Heiko Stuebner
2026-05-25 16:43 ` Conor Dooley [this message]
2026-05-25 16:43 ` Conor Dooley
2026-05-22 17:49 ` [PATCH 2/3] dt-bindings: arm: rockchip: Add Axelera AI Metis Compute Board Patrick Barsanti
2026-05-22 17:49 ` Patrick Barsanti
2026-05-25 16:44 ` Conor Dooley
2026-05-25 16:44 ` Conor Dooley
2026-05-22 17:49 ` [PATCH 3/3] arm64: dts: rockchip: Add Axelera AI metis-sbc Patrick Barsanti
2026-05-22 17:49 ` Patrick Barsanti
2026-05-22 18:21 ` sashiko-bot
2026-05-25 20:54 ` Heiko Stuebner
2026-05-25 20:54 ` Heiko Stuebner
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=20260525-prototype-dingbat-1aa80f9a112e@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael@amarulasolutions.com \
--cc=patrick.barsanti@amarulasolutions.com \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.