[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5AB0E3D5.6090301@easystack.cn>
Date: Tue, 20 Mar 2018 18:35:01 +0800
From: Dongsheng Yang <dongsheng.yang@...ystack.cn>
To: Colin King <colin.king@...onical.com>,
Ilya Dryomov <idryomov@...il.com>, Sage Weil <sage@...hat.com>,
Alex Elder <elder@...nel.org>, Jens Axboe <axboe@...nel.dk>,
ceph-devel@...r.kernel.org, linux-block@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rbd: fix spelling mistake: "reregisteration" ->
"re-registration"
Hi Colin,
On 03/19/2018 09:33 PM, Colin King wrote:
> From: Colin Ian King <colin.king@...onical.com>
>
> Trivial fix to spelling mistake in rdb_warn message text
>
> Signed-off-by: Colin Ian King <colin.king@...onical.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
> }
>
> /*
Powered by blists - more mailing lists