From: "Rob Herring (Arm)" <robh@kernel.org>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
heiko@sntech.de, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Ulf Hansson <ulf.hansson@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v3 03/15] dt-bindings: mmc: rockchip-dw-mshc: Add support for rk3562
Date: Fri, 28 Feb 2025 14:16:23 -0600 [thread overview]
Message-ID: <174077378239.3585541.5147136924937452066.robh@kernel.org> (raw)
In-Reply-To: <20250227111913.2344207-4-kever.yang@rock-chips.com>
On Thu, 27 Feb 2025 19:19:01 +0800, Kever Yang wrote:
> The dw-mshc core on Rockchip's RK3562 is the same as the one already
> included in RK3288. Extend the binding accordingly to allow
>
> compatible = "rockchip,rk3562-dw-mshc", "rockchip,rk3288-dw-mshc";
>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> ---
>
> Changes in v3:
> - update commit msg
>
> Changes in v2: None
>
> Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-02-28 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 11:18 [PATCH v3 00/15] rockchip: Add rk3562 SoC and evb support Kever Yang
2025-02-27 11:19 ` [PATCH v3 02/15] dt-bindings: mmc: Add support for rk3562 eMMC Kever Yang
2025-02-28 20:15 ` Rob Herring (Arm)
2025-03-12 11:24 ` Ulf Hansson
2025-02-27 11:19 ` [PATCH v3 03/15] dt-bindings: mmc: rockchip-dw-mshc: Add support for rk3562 Kever Yang
2025-02-28 20:16 ` Rob Herring (Arm) [this message]
2025-03-12 11:24 ` Ulf Hansson
2025-02-27 13:48 ` (subset) [PATCH v3 00/15] rockchip: Add rk3562 SoC and evb support Mark Brown
2025-02-28 22:10 ` 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=174077378239.3585541.5147136924937452066.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=ulf.hansson@linaro.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