All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Li Bin <huawei.libin@huawei.com>, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, guohanjun@huawei.com
Subject: Re: [PATCH] sched: fix typo in error message
Date: Wed, 25 Apr 2018 08:30:29 +0200	[thread overview]
Message-ID: <1524637829.5725.2.camel@gmx.de> (raw)
In-Reply-To: <1524634900-1861-1-git-send-email-huawei.libin@huawei.com>

On Wed, 2018-04-25 at 13:41 +0800, Li Bin wrote:
> Signed-off-by: Li Bin <huawei.libin@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 64cc564..cf15c1c 100644
> --- a/kernel/sched/topology.c
> +++ b/kernel/sched/topology.c
> @@ -1618,7 +1618,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");

That's not a typo, it's a kernel-speak synonym, as are "borked",
b0rked", "b0rken", "busted", "hosed", and lord knows how many other
colorful variants.  Non-native English speakers beware.

	-Mike

  reply	other threads:[~2018-04-25  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25  5:41 [PATCH] sched: fix typo in error message Li Bin
2018-04-25  6:30 ` Mike Galbraith [this message]
2018-04-25  7:06 ` Peter Zijlstra

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=1524637829.5725.2.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=guohanjun@huawei.com \
    --cc=huawei.libin@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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.