From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Oleg Keri <okerixx@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Sumit Gupta <sumitg@nvidia.com>,
Prasanna Kumar T S M <ptsm@linux.microsoft.com>,
Beata Michalska <beata.michalska@arm.com>,
Russell King <linux@armlinux.org.uk>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Sudeep Holla <sudeep.holla@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] arm64: topology: fix arch_freq_get_on_cpu() overflow above 4.19 GHz
Date: Thu, 17 Sep 2026 12:01:31 +0200 [thread overview]
Message-ID: <6f2907ec-848e-4e60-98b2-a3b7a905b880@arm.com> (raw)
In-Reply-To: <178955779940.30466.10860982419496123467@gmail.com>
Hi Oleg,
On 16.09.26 13:23, Oleg Keri wrote:
> Hi Dietmar,
>
> On Wed, Sep 16, 2026, Dietmar Eggemann wrote:
[...]
> Fine by me, that reads better than open-coding the shift. Your diff
> builds here on arm64 (topology.o and kernel/sched/), so I will fold it
> into v4 and add the scheduler maintainers to Cc for the header move.
>
> Since the diff is yours: is a Suggested-by enough, or would you rather
> have Co-developed-by and your Signed-off-by on the patch?
Don't worry, I will give my 'Reviewed-By' for the final version.
next prev parent reply other threads:[~2026-09-17 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 6:34 [PATCH v3 0/2] arm64/cpufreq: report and track frequencies " Oleg Keri
2026-09-10 6:34 ` [PATCH v3 1/2] arm64: topology: fix arch_freq_get_on_cpu() overflow " Oleg Keri
2026-09-14 7:04 ` Beata Michalska
2026-09-16 10:52 ` Dietmar Eggemann
2026-09-16 11:23 ` Oleg Keri
2026-09-17 10:01 ` Dietmar Eggemann [this message]
2026-09-10 6:34 ` [PATCH v3 2/2] cpufreq: update capacity_freq_ref when the boost state changes Oleg Keri
2026-09-17 9:57 ` Dietmar Eggemann
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=6f2907ec-848e-4e60-98b2-a3b7a905b880@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=beata.michalska@arm.com \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=okerixx@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=ptsm@linux.microsoft.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=sumitg@nvidia.com \
--cc=viresh.kumar@linaro.org \
--cc=will@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
all inboxes | Powered by JetHome®