From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Onur" <work@onurozkan.dev>, "Viresh Kumar" <viresh.kumar@linaro.org>
Cc: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"ojeda@kernel.org" <ojeda@kernel.org>,
"alex.gaynor@gmail.com" <alex.gaynor@gmail.com>,
"boqun.feng@gmail.com" <boqun.feng@gmail.com>,
"gary@garyguo.net" <gary@garyguo.net>,
"bjorn3_gh@protonmail.com" <bjorn3_gh@protonmail.com>,
"lossin@kernel.org" <lossin@kernel.org>,
"a.hindborg@kernel.org" <a.hindborg@kernel.org>,
"aliceryhl@google.com" <aliceryhl@google.com>,
"tmgross@umich.edu" <tmgross@umich.edu>,
"dakr@kernel.org" <dakr@kernel.org>
Subject: Re: [PATCH] Various improvements on clock abstractions
Date: Thu, 19 Jun 2025 22:48:18 +0900 [thread overview]
Message-ID: <DAQK2C3GQ5MB.1XV256W5V0ZTY@nvidia.com> (raw)
In-Reply-To: <20250619130551.388da2a2@nimda>
On Thu Jun 19, 2025 at 7:05 PM JST, Onur wrote:
> On Thu, 19 Jun 2025 12:15:34 +0530
> Viresh Kumar <viresh.kumar@linaro.org> wrote:
>
>> On 17-06-25, 08:55, Miguel Ojeda wrote:
>> > On Tue, Jun 17, 2025 at 6:28 AM Onur Özkan <work@onurozkan.dev>
>> > wrote:
>> > >
>> > > Yes, it should be "Onur Özkan", sorry. Should I update that part
>> > > and re-send the patch?
>> >
>> > I would suggest to wait for other feedback, and then you can send a
>> > v2 if needed.
>> >
>> > > where my patch converts this into a single straight line which I
>> > > think makes it more idiomatic.
>> >
>> > Up to the maintainers :) So far we have both styles around.
>>
>> I am okay with all the changes, the commit log can be improved as you
>> mentioned earlier.
>>
>> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>>
>
> FWIW I split this patch into 3 parts and sent them separately as it
> was suggested earlier by Alexandre.
>
> Here are the patches I sent yesterday:
>
> - https://lore.kernel.org/all/20250618092810.29370-1-work@onurozkan.dev/
> - https://lore.kernel.org/all/20250618093508.16343-1-work@onurozkan.dev/
> - https://lore.kernel.org/all/20250618091442.29104-1-work@onurozkan.dev/
These look good! Small nit for next time: since they are closely
related, please send them as a series to make review (and merging, as
they will conflict if not applied in the right order) easier.
next prev parent reply other threads:[~2025-06-19 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 20:01 [PATCH] Various improvements on clock abstractions onur-ozkan
2025-06-16 20:40 ` Miguel Ojeda
[not found] ` <42151750134012@mail.yandex.com>
2025-06-17 6:55 ` Miguel Ojeda
2025-06-19 6:45 ` Viresh Kumar
2025-06-19 10:05 ` Onur
2025-06-19 13:48 ` Alexandre Courbot [this message]
2025-06-17 7:52 ` Alexandre Courbot
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=DAQK2C3GQ5MB.1XV256W5V0ZTY@nvidia.com \
--to=acourbot@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mturquette@baylibre.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tmgross@umich.edu \
--cc=viresh.kumar@linaro.org \
--cc=work@onurozkan.dev \
/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