From: Krzysztof Kozlowski <krzk@kernel.org>
To: Raghav Sharma <raghav.s@samsung.com>,
s.nawrocki@samsung.com, cw00.choi@samsung.com,
mturquette@baylibre.com, sboyd@kernel.org,
richardcochran@gmail.com, alim.akhtar@samsung.com
Cc: linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v1] clk: samsung: exynosautov920: add block hsi2 clock support
Date: Fri, 9 May 2025 15:30:04 +0200 [thread overview]
Message-ID: <27b7dabc-64e2-4901-bdcb-441388b5304a@kernel.org> (raw)
In-Reply-To: <20250509131210.3192208-1-raghav.s@samsung.com>
On 09/05/2025 15:12, Raghav Sharma wrote:
> Register compatible and cmu_info data to support clocks.
> CMU_HSI2, this provides clocks for HSI2 block
>
> Signed-off-by: Raghav Sharma <raghav.s@samsung.com>
> ---
> drivers/clk/samsung/clk-exynosautov920.c | 72 ++++++++++++++++++++++++
> 1 file changed, 72 insertions(+)
That's some mess. You sent three separate patches, some duplicated, not
threaded, without bindings. Look at mailing list to learn how such
submission should look like.
Read carefully maintainer soc profiles listed under SAMSUNG maintainer's
entry.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-09 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250509130226epcas5p3cf112ae8a2911c76f02756a386c09e62@epcas5p3.samsung.com>
2025-05-09 13:12 ` [PATCH v1] clk: samsung: exynosautov920: add block hsi2 clock support Raghav Sharma
2025-05-09 13:30 ` Krzysztof Kozlowski [this message]
2025-05-10 0:42 ` kernel test robot
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=27b7dabc-64e2-4901-bdcb-441388b5304a@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=raghav.s@samsung.com \
--cc=richardcochran@gmail.com \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@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 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).