From: Maxime Ripard <maxime@cerno.tech>
To: Frank Oltmanns <frank@oltmanns.dev>
Cc: Andre Przywara <andre.przywara@arm.com>,
Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Roman Beranek <me@crly.cz>, Samuel Holland <samuel@sholland.org>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev
Subject: Re: [PATCH 0/2] clk: sunxi-ng: Consider alternative parent rates when determining NKM clock rate
Date: Wed, 7 Jun 2023 14:27:46 +0200 [thread overview]
Message-ID: <vvmdk3fqtjt3jspxgvlbypdxajchymydshya5b5ivk3wfodwwr@yyi26m6toosh> (raw)
In-Reply-To: <87legv2093.fsf@oltmanns.dev>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
On Wed, Jun 07, 2023 at 09:35:20AM +0200, Frank Oltmanns wrote:
> So, my question: Is spending the 30 ms fine or do I need to optimize for
> speed in order for this patchset to be accepted? Or is 2 ms also too
> much of an increase, in which case I'm out of ideas. :-)
You keep mentioning it, but it's really not clear to me why you think
that both are intertwined, or depend on one another?
What's wrong with just merging (some later version of) this series?
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-06-07 12:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 19:07 [PATCH 0/2] clk: sunxi-ng: Consider alternative parent rates when determining NKM clock rate Frank Oltmanns
2023-06-05 19:07 ` [PATCH 1/2] clk: sunxi-ng: nkm: consider alternative parent rates when finding rate Frank Oltmanns
2023-06-07 6:38 ` Maxime Ripard
2023-06-07 7:39 ` Frank Oltmanns
2023-06-12 12:19 ` Maxime Ripard
2023-06-12 16:29 ` Frank Oltmanns
2023-06-13 9:10 ` Maxime Ripard
2023-06-13 10:17 ` Frank Oltmanns
2023-06-13 15:30 ` Maxime Ripard
2023-06-15 16:04 ` Frank Oltmanns
2023-06-19 16:36 ` Maxime Ripard
2023-06-19 8:16 ` Frank Oltmanns
2023-06-19 18:05 ` Maxime Ripard
2023-06-20 18:51 ` Frank Oltmanns
2023-06-26 16:45 ` Maxime Ripard
2023-07-12 4:39 ` Frank Oltmanns
2023-07-17 14:06 ` Maxime Ripard
2023-07-23 8:59 ` Frank Oltmanns
2023-07-25 13:55 ` Maxime Ripard
2023-07-30 14:35 ` Frank Oltmanns
2023-06-05 19:07 ` [PATCH 2/2] clk: sunxi-ng: a64: allow pll-mipi to set parent's rate Frank Oltmanns
2023-06-07 7:35 ` [PATCH 0/2] clk: sunxi-ng: Consider alternative parent rates when determining NKM clock rate Frank Oltmanns
2023-06-07 12:27 ` Maxime Ripard [this message]
2023-06-08 9:29 ` Frank Oltmanns
2023-06-12 8:53 ` Maxime Ripard
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=vvmdk3fqtjt3jspxgvlbypdxajchymydshya5b5ivk3wfodwwr@yyi26m6toosh \
--to=maxime@cerno.tech \
--cc=andre.przywara@arm.com \
--cc=frank@oltmanns.dev \
--cc=jernej.skrabec@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=me@crly.cz \
--cc=mturquette@baylibre.com \
--cc=samuel@sholland.org \
--cc=sboyd@kernel.org \
--cc=wens@csie.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).