From: Conor Dooley <conor@kernel.org>
To: HystericalDragons@proton.me
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
jensen <jensenhuang@friendlyarm.com>
Subject: Re: [PATCH 1/2] dt-bindings: arm: rockchip: Add FriendlyElec NanoPi R28S
Date: Mon, 7 Sep 2026 18:35:11 +0100 [thread overview]
Message-ID: <20260907-skydiver-precise-a8166e576510@spud> (raw)
In-Reply-To: <20260905-r28s-upstream-v1-1-f68d5389269a@proton.me>
[-- Attachment #1.1: Type: text/plain, Size: 75 bytes --]
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable
[-- 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: HystericalDragons@proton.me
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
jensen <jensenhuang@friendlyarm.com>
Subject: Re: [PATCH 1/2] dt-bindings: arm: rockchip: Add FriendlyElec NanoPi R28S
Date: Mon, 7 Sep 2026 18:35:11 +0100 [thread overview]
Message-ID: <20260907-skydiver-precise-a8166e576510@spud> (raw)
In-Reply-To: <20260905-r28s-upstream-v1-1-f68d5389269a@proton.me>
[-- Attachment #1: Type: text/plain, Size: 75 bytes --]
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-09-07 17:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 11:17 [PATCH 0/2] arm64: dts: rockchip: Add FriendlyElec NanoPi R28S 安容 via B4 Relay
2026-09-05 11:17 ` 安容
2026-09-05 11:17 ` 安容 via B4 Relay
2026-09-05 11:17 ` [PATCH 1/2] dt-bindings: arm: " 安容 via B4 Relay
2026-09-05 11:17 ` 安容
2026-09-05 11:17 ` 安容 via B4 Relay
2026-09-07 17:35 ` Conor Dooley [this message]
2026-09-07 17:35 ` Conor Dooley
2026-09-05 11:17 ` [PATCH 2/2] arm64: dts: rockchip: Add devicetree for the " 安容 via B4 Relay
2026-09-05 11:17 ` 安容
2026-09-05 11:17 ` 安容 via B4 Relay
2026-09-07 11:40 ` Chukun Pan
2026-09-07 11:40 ` Chukun Pan
-- strict thread matches above, loose matches on Subject: below --
2026-09-08 23:58 [PATCH 1/2] dt-bindings: arm: rockchip: Add " Andrey Korshunov
2026-09-08 23:58 ` Andrey Korshunov
2026-09-09 10:29 ` Diederik de Haas
2026-09-09 10:29 ` Diederik de Haas
2026-09-09 13:47 ` Andrey Korshunov
2026-09-09 13:47 ` Andrey Korshunov
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=20260907-skydiver-precise-a8166e576510@spud \
--to=conor@kernel.org \
--cc=HystericalDragons@proton.me \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jensenhuang@friendlyarm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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.