From: Peter Zijlstra <peterz@infradead.org>
To: Christian Loehle <christian.loehle@arm.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
vincent.guittot@linaro.org, qyousef@layalina.io,
daniel.lezcano@linaro.org, rostedt@goodmis.org,
dietmar.eggemann@arm.com, Juri Lelli <juri.lelli@redhat.com>
Subject: Re: [PATCH 0/4] sched/deadline: nanoseconds clarifications
Date: Mon, 9 Sep 2024 15:25:08 +0200 [thread overview]
Message-ID: <20240909132508.GD4723@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <1f5f7643-8743-40f4-80ac-0534affd70cd@arm.com>
On Mon, Sep 09, 2024 at 02:01:38PM +0100, Christian Loehle wrote:
> On 8/13/24 17:02, Juri Lelli wrote:
> > Hi,
> >
> > On 13/08/24 15:43, Christian Loehle wrote:
> >> A couple of clarifications about the time units for the deadline
> >> parameters uncovered in the discussion around
> >> https://lore.kernel.org/lkml/3c726cf5-0c94-4cc6-aff0-a453d840d452@arm.com/
> >>
> >> While at it I changed the documentation example to chrt instead
> >> of the schedtool fork.
> >>
> >> No functional changes.
> >
> > Looks good to me!
> >
> > At least for docs/uapi,
> >
> > Acked-by: Juri Lelli <juri.lelli@redhat.com>
>
> (gentle ping)
> Peter, do you want to take {1,2} and Rafael {3,4}?
I'll queue the lot if that is okay with Rafael.
next prev parent reply other threads:[~2024-09-09 13:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 14:43 [PATCH 0/4] sched/deadline: nanoseconds clarifications Christian Loehle
2024-08-13 14:43 ` [PATCH 1/4] sched/deadline: Convert schedtool example to chrt Christian Loehle
2024-09-10 8:09 ` [tip: sched/core] " tip-bot2 for Christian Loehle
2024-09-11 9:32 ` tip-bot2 for Christian Loehle
2024-08-13 14:43 ` [PATCH 2/4] sched/deadline: Clarify nanoseconds in uapi Christian Loehle
2024-09-10 8:09 ` [tip: sched/core] " tip-bot2 for Christian Loehle
2024-09-11 9:32 ` tip-bot2 for Christian Loehle
2024-08-13 14:43 ` [PATCH 3/4] cpufreq/cppc: Use NSEC_PER_MSEC for deadline task Christian Loehle
2024-09-10 8:09 ` [tip: sched/core] " tip-bot2 for Christian Loehle
2024-09-11 9:32 ` tip-bot2 for Christian Loehle
2024-08-13 14:43 ` [PATCH 4/4] sched/cpufreq: " Christian Loehle
2024-09-09 13:38 ` Vincent Guittot
2024-09-10 8:09 ` [tip: sched/core] " tip-bot2 for Christian Loehle
2024-09-11 9:32 ` tip-bot2 for Christian Loehle
2024-08-13 16:02 ` [PATCH 0/4] sched/deadline: nanoseconds clarifications Juri Lelli
2024-09-09 13:01 ` Christian Loehle
2024-09-09 13:25 ` Peter Zijlstra [this message]
2024-09-09 16:39 ` Rafael J. Wysocki
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=20240909132508.GD4723@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=christian.loehle@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=qyousef@layalina.io \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.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