public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Colin King <colin.king@canonical.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] locking/ww_mutex: fix spelling mistake "cylic" -> "cyclic"
Date: Tue, 28 Aug 2018 18:39:52 +0100	[thread overview]
Message-ID: <20180828173951.GB20375@arm.com> (raw)
In-Reply-To: <20180824112235.8842-1-colin.king@canonical.com>

On Fri, Aug 24, 2018 at 12:22:35PM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> Trivial fix to spelling mistake in pr_err error message
> 
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  kernel/locking/test-ww_mutex.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Given that this is part of an error message, I agree it's worth fixing.

Will

> diff --git a/kernel/locking/test-ww_mutex.c b/kernel/locking/test-ww_mutex.c
> index 5b915b370d5a..0be047dbd897 100644
> --- a/kernel/locking/test-ww_mutex.c
> +++ b/kernel/locking/test-ww_mutex.c
> @@ -324,7 +324,7 @@ static int __test_cycle(unsigned int nthreads)
>  		if (!cycle->result)
>  			continue;
>  
> -		pr_err("cylic deadlock not resolved, ret[%d/%d] = %d\n",
> +		pr_err("cyclic deadlock not resolved, ret[%d/%d] = %d\n",
>  		       n, nthreads, cycle->result);
>  		ret = -EINVAL;
>  		break;
> -- 
> 2.17.1
> 

  reply	other threads:[~2018-08-28 17:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24 11:22 [PATCH] locking/ww_mutex: fix spelling mistake "cylic" -> "cyclic" Colin King
2018-08-28 17:39 ` Will Deacon [this message]
2018-09-10 12:39 ` [tip:locking/urgent] locking/ww_mutex: Fix " tip-bot for Colin Ian King
  -- strict thread matches above, loose matches on Subject: below --
2017-03-30  9:22 [PATCH] locking/ww_mutex: fix spelling mistake: " Colin King

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=20180828173951.GB20375@arm.com \
    --to=will.deacon@arm.com \
    --cc=colin.king@canonical.com \
    --cc=kernel-janitors@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox