All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 29 Sep 2023 12:57:53 +0200	[thread overview]
Message-ID: <ZRatsTz1mQRFJ0sW@lothringen> (raw)
In-Reply-To: <ZRVCNeMcSQcXS36N@gmail.com>

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...

> 
> >   */
> >  static void tick_nohz_lowres_handler(struct clock_event_device *dev)
> >  {
> 
> As well-deserved penace for my nitpicking, I've fixed these on top of
> tip:timers/core, and have also done a full scan of kernel/time/tick-sched.c
> for spelling, consistency of style and readability of comments - see
> the patch below.
> 
> Thanks,
> 
> 	Ingo
> 
> ===========================>
> From: Ingo Molnar <mingo@kernel.org>
> Date: Thu, 28 Sep 2023 10:45:54 +0200
> Subject: [PATCH] tick/nohz: Update comments some more
> 
> Inspired by recent enhancements to comments in kernel/time/tick-sched.c,
> go through the entire file and fix/unify its comments:
> 
>  - Fix over a dozen typos, spelling mistakes & cases of bad grammar.
> 
>  - Re-phrase sentences that I needed to read three times to understand.
> 
>     [ I used the following arbitrary rule-of-thumb:
>        - if I had to read a comment twice, it was usually my fault,
>        - if I had to read it a third time, it was the comment's fault. ]
> 
>  - Comma updates:
> 
>     - Add commas where needed
> 
>     - Remove commas where not needed
> 
>     - In cases where a comma is optional, choose one variant and try to
>       standardize it over similar sentences in the file.   
> 
>  - Standardize on standalone 'NOHZ' spelling in free-flowing comments:
> 
>       s/nohz/NOHZ
>       s/no idle tick/NOHZ
> 
>    Still keep 'dynticks' as a popular synonym.
> 
>  - Standardize on referring to variable names within free-flowing
>    comments with the "'var'" nomenclature, and function names as
>    "function_name()".
> 
>  - Standardize on '64-bit' and '32-bit':
>      s/32bit/32-bit
>      s/64bit/64-bit
> 
>  - Standardize on 'IRQ work':
>      s/irq work/IRQ work
> 
>  - A few other tidyups I probably missed to list.
> 
> No change in functionality intended - other than one small change to
> a syslog output string.
> 
> Signed-off-by: Ingo Molnar <mingo@kernel.org>

Looks good, thanks!

  parent reply	other threads:[~2023-09-29 10:58 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 [this message]
2023-09-29 21:09         ` Ingo Molnar
2023-09-29 22:05           ` Frederic Weisbecker
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=ZRatsTz1mQRFJ0sW@lothringen \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.