From: "sunyeal.hong" <sunyeal.hong@samsung.com>
To: "'Krzysztof Kozlowski'" <krzk@kernel.org>,
"'Sylwester Nawrocki'" <s.nawrocki@samsung.com>,
"'Chanwoo Choi'" <cw00.choi@samsung.com>,
"'Alim Akhtar'" <alim.akhtar@samsung.com>,
"'Michael Turquette'" <mturquette@baylibre.com>,
"'Stephen Boyd'" <sboyd@kernel.org>,
"'Rob Herring'" <robh@kernel.org>,
"'Conor Dooley'" <conor+dt@kernel.org>
Cc: <linux-samsung-soc@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 0/3] add clocks support for exynosauto v920 SoC
Date: Mon, 7 Oct 2024 16:30:35 +0900 [thread overview]
Message-ID: <00a401db188a$cc7a1d30$656e5790$@samsung.com> (raw)
In-Reply-To: <459e2af0-16a1-45aa-93b8-50b84b359854@kernel.org>
Hello Krzyszto,
> -----Original Message-----
> From: Krzysztof Kozlowski <krzk@kernel.org>
> Sent: Monday, October 7, 2024 4:20 PM
> To: Sunyeal Hong <sunyeal.hong@samsung.com>; Sylwester Nawrocki
> <s.nawrocki@samsung.com>; Chanwoo Choi <cw00.choi@samsung.com>; Alim
> Akhtar <alim.akhtar@samsung.com>; Michael Turquette
> <mturquette@baylibre.com>; Stephen Boyd <sboyd@kernel.org>; Rob Herring
> <robh@kernel.org>; Conor Dooley <conor+dt@kernel.org>
> Cc: linux-samsung-soc@vger.kernel.org; linux-clk@vger.kernel.org;
> devicetree@vger.kernel.org; linux-arm-kernel@lists.infradead.org; linux-
> kernel@vger.kernel.org
> Subject: Re: [PATCH v2 0/3] add clocks support for exynosauto v920 SoC
>
> On 07/10/2024 09:18, Sunyeal Hong wrote:
> > This patchset adds the CMU block below to support exynosauto v920 SoC.
> > - CMU_PERIC1
> > - CMU_MISC
> > - CMU_HSI0/1
> >
> > Changes in v2:
> > - Rebase the patch to reflect the latest fixes
>
> Not much improved. Still blind rebase without addressing the issue I
> pointed out.
>
> Allow people to actually review your patches, instead of sending multiple
> versions within 5 minutes.
>
> One patchset per 24h.
>
I apologize for sending you the patch version incorrectly multiple times.
Could you elaborate a bit more on the "unrelated change" part you mentioned in the comment?
I don't think I understand your exact intention.
Best Regards,
sunyeal
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2024-10-07 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241007071833epcas2p213100b34fd5a8192497a41e2e455947a@epcas2p2.samsung.com>
2024-10-07 7:18 ` [PATCH v2 0/3] add clocks support for exynosauto v920 SoC Sunyeal Hong
2024-10-07 7:18 ` [PATCH v2 1/3] dt-bindings: clock: exynosautov920: add peric1, misc and hsi0/1 clock definitions Sunyeal Hong
2024-10-07 7:18 ` [PATCH v2 2/3] clk: samsung: exynosautov920: add peric1, misc and hsi0/1 clock support Sunyeal Hong
2024-10-07 7:18 ` [PATCH v2 3/3] arm64: dts: exynosautov920: add peric1, misc and hsi0/1 clock DT nodes Sunyeal Hong
2024-10-07 7:20 ` [PATCH v2 0/3] add clocks support for exynosauto v920 SoC Krzysztof Kozlowski
2024-10-07 7:30 ` sunyeal.hong [this message]
2024-10-07 7:48 ` 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='00a401db188a$cc7a1d30$656e5790$@samsung.com' \
--to=sunyeal.hong@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--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=robh@kernel.org \
--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 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.