public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	linux-kernel@vger.kernel.org,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH] rcu: Fix various typos in comments
Date: Tue, 23 Mar 2021 12:17:53 +0100	[thread overview]
Message-ID: <20210323111753.GB3939639@gmail.com> (raw)
In-Reply-To: <20210323053618.GU2696@paulmck-ThinkPad-P72>


* Paul E. McKenney <paulmck@kernel.org> wrote:

> > >  * there are no read-side primitives analogous to rcu_read_lock() and
> > >  * rcu_read_unlock() because this primitive is intended to determine
> > >  * that all tasks have passed through a safe state, not so much for
> > > - * data-strcuture synchronization.
> > > + * data-structure synchronization.
> > >  *
> > 
> > The "hyphen" in the middle of the word "data structure" is required or keeping by
> > convention or has some significance?
> 
> Yes, this is one of many peculiarities of English, and an optional one
> at that.  English is not a block-structured language, so grouping can
> be ambiguous.  Is is "(data structure) synchronization" or is it instead
> "data (structure synchronization)"?  The default is the latter, and
> the hyphen indicates the former.  In this case, the former is intended,
> hence the hyphen.

The other point is that there are a *lot* of hyphen variations in the 
kernel, and unless the primary author or maintainer is iterating the 
text would be insane to categorize them as 'typos' and create churn to 
'fix' them...

'data-structure' or 'datastructure' are both perfectly readable, just 
like 'fast-path' or 'fastpath', 'cache-miss' or 'cachemiss' and a 
million other examples.

Thanks,

	Ingo

  reply	other threads:[~2021-03-23 11:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 23:02 [PATCH] rcu: Fix various typos in comments Ingo Molnar
2021-03-23  2:55 ` Randy Dunlap
2021-03-23  5:32   ` Paul E. McKenney
2021-03-23  2:56 ` Bhaskar Chowdhury
2021-03-23  5:36   ` Paul E. McKenney
2021-03-23 11:17     ` Ingo Molnar [this message]
2021-03-23 16:20       ` Paul E. McKenney

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=20210323111753.GB3939639@gmail.com \
    --to=mingo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=unixbhaskar@gmail.com \
    /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