From: Kwanghoon Son <k.son@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: s.nawrocki@samsung.com, cw00.choi@samsung.com,
alim.akhtar@samsung.com, mturquette@baylibre.com,
sboyd@kernel.org, robh@kernel.org, conor+dt@kernel.org,
tomasz.figa@gmail.com, linux-samsung-soc@vger.kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] dt-bindings: clk: exynosautov9: add dpum clock definitions
Date: Tue, 30 Jul 2024 14:49:34 +0900 [thread overview]
Message-ID: <Zqh-7jHUoFPVS_Cp@mediavision> (raw)
In-Reply-To: <32d3c894-64ba-40ac-aef4-988c3f90c2a1@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On Mon, Jul 29, 2024 at 08:03:49AM +0200, Krzysztof Kozlowski wrote:
> On 29/07/2024 06:30, Kwanghoon Son wrote:
> > Add dpum clk definitions.
> >
> > Signed-off-by: Kwanghoon Son <k.son@samsung.com>
> > ---
> > include/dt-bindings/clock/samsung,exynosautov9.h | 11 +++++++++++
> > 1 file changed, 11 insertions(+)
> >
>
> Why using different subject prefixes for binding patches?
>
> Anyway, headers go with the schema/bindings file.
Thanks for feedback. I'll squash patch 1,2 in v2.
Kwang.
>
> Best regards,
> Krzysztof
>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2024-07-30 5:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240729043102epcas1p4952d0437ef733036b8fdbe28b0ef21ca@epcas1p4.samsung.com>
2024-07-29 4:30 ` [PATCH 0/4] dpum clock support for Exynos Auto v9 SoC Kwanghoon Son
2024-07-29 4:30 ` [PATCH 1/4] dt-bindings: clk: exynosautov9: add dpum clock definitions Kwanghoon Son
2024-07-29 6:03 ` Krzysztof Kozlowski
2024-07-30 5:49 ` Kwanghoon Son [this message]
2024-07-29 4:30 ` [PATCH 2/4] dt-bindings: clock: exynosautov9: add schema for dpum Kwanghoon Son
2024-07-29 4:30 ` [PATCH 3/4] arm64: dts: exynosautov9: add dpum clock DT nodes Kwanghoon Son
2024-07-29 4:30 ` [PATCH 4/4] clk: samsung: exynosautov9: add dpum clock support Kwanghoon Son
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=Zqh-7jHUoFPVS_Cp@mediavision \
--to=k.son@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-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=tomasz.figa@gmail.com \
/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