From: Frederic Weisbecker <frederic@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
linux-tip-commits@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] tick/nohz: Update comments some more
Date: Sat, 30 Sep 2023 00:05:30 +0200 [thread overview]
Message-ID: <ZRdKKiQAgU1btl7V@localhost.localdomain> (raw)
In-Reply-To: <ZRc9BN+Mv3HnN9GL@gmail.com>
Le Fri, Sep 29, 2023 at 11:09:24PM +0200, Ingo Molnar a écrit :
>
> * Frederic Weisbecker <frederic@kernel.org> wrote:
>
> > On Thu, Sep 28, 2023 at 11:07:01AM +0200, Ingo Molnar wrote:
> > > > + * infrastructure actually relies on the tick itself as a backend in
> > > > + * low-resolution mode (see hrtimer_run_queues()).
> > > > + *
> > > > + * This low-resolution handler still makes use of some hrtimer APIs meanwhile
> > > > + * for commodity with expiration calculation and forwarding.
> > >
> > > commodity?
> >
> > I meant 'convenience', my usual frenglish issues...
>
> 'Convenience' it is. :-)
>
> > Looks good, thanks!
>
> Thanks, I've applied the patch to tip:timers/core, with your Acked-by added.
Sounds good, thanks!
next prev parent reply other threads:[~2023-09-29 22:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 10:44 [PATCH 0/5] tick/nohz: cleanups and fixes v2 Frederic Weisbecker
2023-09-12 10:44 ` [PATCH 1/5] tick/nohz: Rename the tick handlers to more self-explanatory names Frederic Weisbecker
2023-09-27 15:01 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2023-09-12 10:44 ` [PATCH 2/5] tick/nohz: Update obsolete comments Frederic Weisbecker
2023-09-27 15:01 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2023-09-28 9:07 ` [PATCH] tick/nohz: Update comments some more Ingo Molnar
2023-09-28 9:11 ` Ingo Molnar
2023-09-29 10:57 ` Frederic Weisbecker
2023-09-29 21:09 ` Ingo Molnar
2023-09-29 22:05 ` Frederic Weisbecker [this message]
2023-09-29 21:12 ` [tip: timers/core] " tip-bot2 for Ingo Molnar
2023-09-12 10:44 ` [PATCH 3/5] tick/nohz: Don't shutdown the lowres tick from itself Frederic Weisbecker
2023-09-14 1:17 ` Joel Fernandes
2023-09-14 9:29 ` Frederic Weisbecker
2023-09-14 13:26 ` Joel Fernandes
2023-09-27 15:01 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2023-09-12 10:44 ` [PATCH 4/5] tick/nohz: remove unused tick_nohz_idle_stop_tick_protected() Frederic Weisbecker
2023-09-27 15:01 ` [tip: timers/core] tick/nohz: Remove " tip-bot2 for Xueshi Hu
2023-09-12 10:44 ` [PATCH 5/5] timers: Tag (hr)timer softirq as hotplug safe Frederic Weisbecker
2023-09-16 1:38 ` Joel Fernandes
2023-09-18 17:04 ` Thomas Gleixner
2023-09-27 15:01 ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
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=ZRdKKiQAgU1btl7V@localhost.localdomain \
--to=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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