From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: John Stultz <jstultz@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] sched_clock: Fixes for frequency reporting
Date: Sun, 24 Apr 2022 12:47:15 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2204211556270.9383@angie.orcam.me.uk> (raw)
Hi,
Hmm, kernel/time/sched_clock.c lacks a MAINTAINERS entry, but I guess it
goes along with either high-resolution timers or clocksource core. Please
advise otherwise.
In the course of reviewing the MIPS part of the `random_get_entropy'
patch set recently posted I have noticed the odd rounding mode used for
clock source frequency reporting, and then upon inspecting code involved
I've come across a couple of further small issues.
This patch set addresses these issues. Please see individual change
descriptions for details.
Maciej
next reply other threads:[~2022-04-24 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 11:47 Maciej W. Rozycki [this message]
2022-04-24 11:47 ` [PATCH 1/3] sched_clock: Round the frequency reported to nearest rather than down Maciej W. Rozycki
2022-04-26 20:38 ` John Stultz
2022-05-02 12:31 ` [tip: timers/core] time/sched_clock: " tip-bot2 for Maciej W. Rozycki
2022-04-24 11:47 ` [PATCH 2/3] sched_clock: Use Hz as the unit for clock rate reporting below 4kHz Maciej W. Rozycki
2022-05-02 12:31 ` [tip: timers/core] time/sched_clock: " tip-bot2 for Maciej W. Rozycki
2022-04-24 11:47 ` [PATCH 3/3] sched_clock: Fix formatting of frequency reporting code Maciej W. Rozycki
2022-04-26 20:41 ` John Stultz
2022-05-02 12:31 ` [tip: timers/core] time/sched_clock: " tip-bot2 for Maciej W. Rozycki
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=alpine.DEB.2.21.2204211556270.9383@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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).