linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Zhang Jiaming <jiaming@nfschina.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	liqiong@nfschina.com, renyu@nfschina.com, song@kernel.org
Subject: Re: [PATCH] block: Fix spelling mistake in comments
Date: Mon, 4 Jul 2022 09:51:46 +0200	[thread overview]
Message-ID: <a4aeb494-7ffd-86ee-856f-5d3091cdb705@molgen.mpg.de> (raw)
In-Reply-To: <20220704012328.6507-1-jiaming@nfschina.com>

Dear Zhang,


Thank you for your patch. Some nits.

Am 04.07.22 um 03:23 schrieb Zhang Jiaming:
> There are some typos(dones't, waitting) in comments.
> Fix it.

Please add a space before the (. “Fix it.” also fits on the line above, 
and maybe use plural in the commit message summary. For the body, maybe:

Fix spelling of dones't and waitting in comments.

> Signed-off-by: Zhang Jiaming <jiaming@nfschina.com>
> ---
>   drivers/md/raid5-cache.c | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/md/raid5-cache.c b/drivers/md/raid5-cache.c
> index 83c184eddbda..4b799005eb6e 100644
> --- a/drivers/md/raid5-cache.c
> +++ b/drivers/md/raid5-cache.c
> @@ -125,7 +125,7 @@ struct r5l_log {
>   					 * reclaimed.  if it's 0, reclaim spaces
>   					 * used by io_units which are in
>   					 * IO_UNIT_STRIPE_END state (eg, reclaim
> -					 * dones't wait for specific io_unit
> +					 * doesn't wait for specific io_unit
>   					 * switching to IO_UNIT_STRIPE_END
>   					 * state) */
>   	wait_queue_head_t iounit_wait;
> @@ -1327,9 +1327,9 @@ static void r5l_write_super_and_discard_space(struct r5l_log *log,
>   	 * superblock is updated to new log tail. Updating superblock (either
>   	 * directly call md_update_sb() or depend on md thread) must hold
>   	 * reconfig mutex. On the other hand, raid5_quiesce is called with
> -	 * reconfig_mutex hold. The first step of raid5_quiesce() is waitting
> -	 * for all IO finish, hence waitting for reclaim thread, while reclaim
> -	 * thread is calling this function and waitting for reconfig mutex. So
> +	 * reconfig_mutex hold. The first step of raid5_quiesce() is waiting
> +	 * for all IO finish, hence waiting for reclaim thread, while reclaim
> +	 * thread is calling this function and waiting for reconfig mutex. So
>   	 * there is a deadlock. We workaround this issue with a trylock.
>   	 * FIXME: we could miss discard if we can't take reconfig mutex
>   	 */

Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>


Kind regards,

Paul

  reply	other threads:[~2022-07-04  7:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04  1:23 [PATCH] block: Fix spelling mistake in comments Zhang Jiaming
2022-07-04  7:51 ` Paul Menzel [this message]
2022-07-04 10:05 ` [PATCH] block: Fix spelling mistakes " Zhang Jiaming
2022-07-04 18:01   ` Daniel K.
2022-07-05  2:26 ` [PATCH v2] " Zhang Jiaming
2022-08-23 17:59   ` Song Liu
2022-08-26  3:08   ` [PATCH v3] md/raid5-cache: Resolve patch confilcts Zhang Jiaming
2022-08-26  5:16     ` Song Liu
2022-08-26 10:44   ` [PATCH v3] block: Fix spelling mistakes in comments Zhang Jiaming

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=a4aeb494-7ffd-86ee-856f-5d3091cdb705@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=jiaming@nfschina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=liqiong@nfschina.com \
    --cc=renyu@nfschina.com \
    --cc=song@kernel.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;
as well as URLs for NNTP newsgroup(s).