mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Daniel K." <d@ja.vu>
To: Zhang Jiaming <jiaming@nfschina.com>, song@kernel.org
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	liqiong@nfschina.com, renyu@nfschina.com,
	Paul Menzel <pmenzel@molgen.mpg.de>
Subject: Re: [PATCH] block: Fix spelling mistakes in comments
Date: Mon, 4 Jul 2022 18:01:22 +0000	[thread overview]
Message-ID: <44f85603-8a34-7654-54cf-987a62e44778@ja.vu> (raw)
In-Reply-To: <20220704100557.6429-1-jiaming@nfschina.com>

On 7/4/22 10:05, Zhang Jiaming wrote:
> Fix spelling of dones't and waitting in comments.

Version your patches, you're now at v2. [PATCH v2] ...

Please find a few suggestions below as to what can be fixed in this
block of text as you're making a pass over it.


> @@ -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

                          held

> +	 * for all IO finish, hence waiting for reclaim thread, while reclaim

              all IO to finish

> +	 * 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
>  	 */

There are several mentions of 'reconfig mutex' that should probably be
'reconfig_mutex'. What's the correct way to refer to a mutex in comments
like the above?


Daniel K.

  reply	other threads:[~2022-07-04 19:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04  1:23 [PATCH] block: Fix spelling mistake " Zhang Jiaming
2022-07-04  7:51 ` Paul Menzel
2022-07-04 10:05 ` [PATCH] block: Fix spelling mistakes " Zhang Jiaming
2022-07-04 18:01   ` Daniel K. [this message]
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=44f85603-8a34-7654-54cf-987a62e44778@ja.vu \
    --to=d@ja.vu \
    --cc=jiaming@nfschina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=liqiong@nfschina.com \
    --cc=pmenzel@molgen.mpg.de \
    --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

all inboxes | Powered by JetHome®