From: Andrey Korshunov <razor1702@gmail.com>
To: diederik@cknow-tech.com
Cc: heiko@sntech.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: rockchip: Add FriendlyElec NanoPi R28S
Date: Wed, 9 Sep 2026 16:47:31 +0300 [thread overview]
Message-ID: <20260909134731.364-1-razor1702@gmail.com> (raw)
In-Reply-To: <DLAPRUR4Q73F.1KIBGA408LQSJ@cknow-tech.com>
On Wed Sep 9, 2026 at 12:29 PM CEST, Diederik de Haas wrote:
> There's already an attempt in the works to upstream NanoPi R28S support:
> https://lore.kernel.org/linux-rockchip/20260907-r28s-upstream-v2-0-21ab570fc91c@proton.me/
Thanks, I had not seen it - I searched lore before sending, evidently not
well enough. That series is further along and covers more of the board,
so please drop mine.
I have the hardware and will review and test that one instead. One
finding about the PHY reset has gone to patch 2 of that thread.
Andrey
WARNING: multiple messages have this Message-ID (diff)
From: Andrey Korshunov <razor1702@gmail.com>
To: diederik@cknow-tech.com
Cc: heiko@sntech.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: rockchip: Add FriendlyElec NanoPi R28S
Date: Wed, 9 Sep 2026 16:47:31 +0300 [thread overview]
Message-ID: <20260909134731.364-1-razor1702@gmail.com> (raw)
In-Reply-To: <DLAPRUR4Q73F.1KIBGA408LQSJ@cknow-tech.com>
On Wed Sep 9, 2026 at 12:29 PM CEST, Diederik de Haas wrote:
> There's already an attempt in the works to upstream NanoPi R28S support:
> https://lore.kernel.org/linux-rockchip/20260907-r28s-upstream-v2-0-21ab570fc91c@proton.me/
Thanks, I had not seen it - I searched lore before sending, evidently not
well enough. That series is further along and covers more of the board,
so please drop mine.
I have the hardware and will review and test that one instead. One
finding about the PHY reset has gone to patch 2 of that thread.
Andrey
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-09-09 13:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 23:58 [PATCH 1/2] dt-bindings: arm: rockchip: Add FriendlyElec NanoPi R28S Andrey Korshunov
2026-09-08 23:58 ` Andrey Korshunov
2026-09-08 23:58 ` [PATCH 2/2] arm64: dts: " Andrey Korshunov
2026-09-08 23:58 ` Andrey Korshunov
2026-09-09 10:29 ` [PATCH 1/2] dt-bindings: arm: " Diederik de Haas
2026-09-09 10:29 ` Diederik de Haas
2026-09-09 13:47 ` Andrey Korshunov [this message]
2026-09-09 13:47 ` Andrey Korshunov
-- strict thread matches above, loose matches on Subject: below --
2026-09-05 11:17 [PATCH 0/2] arm64: dts: " 安容 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
2026-09-07 17:35 ` Conor Dooley
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=20260909134731.364-1-razor1702@gmail.com \
--to=razor1702@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diederik@cknow-tech.com \
--cc=heiko@sntech.de \
--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.