From: Krzysztof Kozlowski <krzk@kernel.org>
To: "ping.gao" <ping.gao@samsung.com>
Cc: shawn.lin@rock-chips.com, ulf.hansson@linaro.org,
jh80.chung@samsung.com, krzk+dt@kernel.org, conor+dt@kernel.org,
robh@kernel.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
hy50.seo@samsung.com, kwangwon.min@samsung.com
Subject: Re: [PATCH v3 3/3] dt-bindings: mmc: synopsys-dw-mshc: No need to enforce setting two clocks
Date: Fri, 27 Feb 2026 08:53:33 +0100 [thread overview]
Message-ID: <d85a5707-66ea-4053-87cb-9f34b7cbbc6e@kernel.org> (raw)
In-Reply-To: <20260227-lively-vivid-wren-8e8a4d@quoll>
On 27/02/2026 08:51, Krzysztof Kozlowski wrote:
> On Thu, Feb 26, 2026 at 05:10:51PM +0800, ping.gao wrote:
>> The driver `dw_mmc.c` now treats the biu clock as optional, so the
>> binding can be relaxed to allow a single clock.
>> Signed-off-by: ping.gao <ping.gao@samsung.com>
>> ---
>> Documentation/devicetree/bindings/mmc/synopsys-dw-mshc.yaml | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> What is this mess in threading? I see here bunch of 15 emails all mixed
> up?
>
> Do not attach (thread) your patchsets to some other threads (unrelated
> or older versions). This buries them deep in the mailbox and might
> interfere with applying entire sets. See also:
> https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830
Plus I found now that you ALREADY sent v3, so you made complete mess in
duplicate and wrongly attached postings.
Slow down and re-think what are you doing.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-27 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260123085150epcas5p42f2cc04843ae7657380b2968261246cb@epcas5p4.samsung.com>
2026-02-26 9:09 ` [PATCH v3 1/3] mmc: dw_mmc-k3: before set biu_clk rate, check biu_clk available or not ping.gao
2026-02-26 9:10 ` [PATCH v3 2/3] mmc: dw_mmc: Using devm_clk_get_optional() for biu_clk ping.gao
2026-02-26 9:10 ` [PATCH v3 3/3] dt-bindings: mmc: synopsys-dw-mshc: No need to enforce setting two clocks ping.gao
2026-02-27 7:50 ` Krzysztof Kozlowski
2026-02-27 7:52 ` Krzysztof Kozlowski
2026-02-27 7:51 ` Krzysztof Kozlowski
2026-02-27 7:53 ` Krzysztof Kozlowski [this message]
2026-02-28 3:13 ` ping.gao
2026-02-28 9:46 ` Krzysztof Kozlowski
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=d85a5707-66ea-4053-87cb-9f34b7cbbc6e@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hy50.seo@samsung.com \
--cc=jh80.chung@samsung.com \
--cc=krzk+dt@kernel.org \
--cc=kwangwon.min@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ping.gao@samsung.com \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.com \
--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