public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] sched/topology: Fix a spelling mistake in error message
Date: Wed, 26 May 2021 08:57:13 +0200	[thread overview]
Message-ID: <YK3xSVbwub51ZnaD@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <5571d34f-1965-8d8e-3033-6352dd0dcaee@huawei.com>

On Wed, May 26, 2021 at 10:42:31AM +0800, Leizhen (ThunderTown) wrote:
> 
> 
> On 2021/5/26 10:32, Randy Dunlap wrote:
> > On 5/25/21 7:18 PM, Zhen Lei wrote:
> >> The misspelled word 'borken' should be 'broken'.
> >>
> >> Fixes: 6ae72dff3759 ("sched: Robustify topology setup")
> >> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> >> ---
> >>  kernel/sched/topology.c | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
> >> index 55a0a243e871..80295e224442 100644
> >> --- a/kernel/sched/topology.c
> >> +++ b/kernel/sched/topology.c
> >> @@ -1937,7 +1937,7 @@ static struct sched_domain *build_sched_domain(struct sched_domain_topology_leve
> >>  
> >>  		if (!cpumask_subset(sched_domain_span(child),
> >>  				    sched_domain_span(sd))) {
> >> -			pr_err("BUG: arch topology borken\n");
> >> +			pr_err("BUG: arch topology broken\n");
> > 
> > Would "borked" or "b0rken" be clearer?
> 
> These two words don't seem to exist at all. Linux is an open-source
> code for the world, so it's better to use a more common word.

Language is a living thing; also:

  https://www.urbandictionary.com/define.php?term=borked

I realize that as a non-native speaker idioms and colloquialisms are
difficult, but if we sanitize the language we'll end up with something
dreadfully dull and less expressive.

Also; this is a rather trivial play on words, to break the word broken,
it should apply to pretty much any (written) language. It should be an
evident pun to all except computer spell checkers (they so lack humour).

Also, I too am a non-native speaker, although I suspect I have it easier
for my native tongue is at least in the same language group as English.


  parent reply	other threads:[~2021-05-26  6:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  2:18 [PATCH 1/1] sched/topology: Fix a spelling mistake in error message Zhen Lei
2021-05-26  2:32 ` Randy Dunlap
2021-05-26  2:42   ` Leizhen (ThunderTown)
2021-05-26  6:52     ` Ingo Molnar
2021-05-27  1:57       ` Leizhen (ThunderTown)
2021-05-26  6:57     ` Peter Zijlstra [this message]
2021-05-26  8:28       ` Leizhen (ThunderTown)
2021-05-26  6:51 ` Ingo Molnar

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=YK3xSVbwub51ZnaD@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=thunder.leizhen@huawei.com \
    --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