Linux block layer
 help / color / mirror / Atom feed
From: Dongsheng Yang <dongsheng.yang@easystack.cn>
To: Colin King <colin.king@canonical.com>,
	Ilya Dryomov <idryomov@gmail.com>, Sage Weil <sage@redhat.com>,
	Alex Elder <elder@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	ceph-devel@vger.kernel.org, linux-block@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rbd: fix spelling mistake: "reregisteration" -> "re-registration"
Date: Tue, 20 Mar 2018 18:35:01 +0800	[thread overview]
Message-ID: <5AB0E3D5.6090301@easystack.cn> (raw)
In-Reply-To: <20180319133310.4251-1-colin.king@canonical.com>

Hi Colin,

On 03/19/2018 09:33 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in rdb_warn message text
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>   drivers/block/rbd.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
> index 1e03b04819c8..7b97240ff15e 100644
> --- a/drivers/block/rbd.c
> +++ b/drivers/block/rbd.c
> @@ -3887,7 +3887,7 @@ static void rbd_reregister_watch(struct work_struct *work)
>   
>   	ret = rbd_dev_refresh(rbd_dev);
>   	if (ret)
> -		rbd_warn(rbd_dev, "reregisteration refresh failed: %d", ret);
> +		rbd_warn(rbd_dev, "re-registration refresh failed: %d", ret);

Hmmm, I am not sure is that a spelling mistake, because the function 
name is rbd_reregister_watch().

Thanx
Yang
>   }
>   
>   /*

  reply	other threads:[~2018-03-20 10:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 13:33 [PATCH] rbd: fix spelling mistake: "reregisteration" -> "re-registration" Colin King
2018-03-20 10:35 ` Dongsheng Yang [this message]
2018-03-20 10:39   ` Colin Ian King
2018-03-20 14:49     ` Ilya Dryomov

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=5AB0E3D5.6090301@easystack.cn \
    --to=dongsheng.yang@easystack.cn \
    --cc=axboe@kernel.dk \
    --cc=ceph-devel@vger.kernel.org \
    --cc=colin.king@canonical.com \
    --cc=elder@kernel.org \
    --cc=idryomov@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sage@redhat.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