From: Diederik de Haas <didi.debian@cknow.org>
To: Dragan Simic <dsimic@manjaro.org>
Cc: Heiko Stuebner <heiko@sntech.de>, Alex Bee <knaerzche@gmail.com>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Johan Jonker <jbx6244@gmail.com>,
Chen-Yu Tsai <wens@csie.org>
Subject: Re: [PATCH v3 1/2] arm64: dts: rockchip: Add sdmmc_ext for RK3328
Date: Sat, 13 Jul 2024 16:35:34 +0200 [thread overview]
Message-ID: <2735059.JVtD0IzA6d@bagend> (raw)
In-Reply-To: <72718d8d02c25993c138567c96340792@manjaro.org>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
Hi Dragan,
Thanks for the reviews!
On Saturday, 13 July 2024 15:45:12 CEST Dragan Simic wrote:
> Looking good to me, cross-referencing the RK3328 TRM and the
> downstream RK3328 SoC dtsi checks out. Though, it will remain inert
> in our codebase, because no supported boards use it, but that's fine,
> we're still improving the correctness of the RK3328 SoC dtsi.
Indeed. But it's hard to argue with technically correct ;-)
Cheers,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-07-13 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 13:28 [PATCH v3 0/2] sdmmc/sdio/emmc improvements for RK3328 Diederik de Haas
2024-07-10 13:28 ` [PATCH v3 1/2] arm64: dts: rockchip: Add sdmmc_ext " Diederik de Haas
2024-07-13 13:45 ` Dragan Simic
2024-07-13 14:35 ` Diederik de Haas [this message]
2024-07-13 14:56 ` Alex Bee
2024-07-13 14:58 ` Dragan Simic
2024-07-10 13:28 ` [PATCH v3 2/2] arm64: dts: rockchip: Add sdmmc/sdio/emmc reset controls " Diederik de Haas
2024-07-13 13:32 ` Dragan Simic
2024-07-29 20:21 ` [PATCH v3 0/2] sdmmc/sdio/emmc improvements " 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=2735059.JVtD0IzA6d@bagend \
--to=didi.debian@cknow.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=knaerzche@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).