From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Yongzhen Zhang <zhangyongzhen@kylinos.cn>, ocfs2-devel@lists.linux.dev
Cc: mark@fasheh.com, jlbec@evilplan.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ocfs2: Spelling fix
Date: Sat, 6 Jan 2024 09:55:51 +0800 [thread overview]
Message-ID: <64d54843-4e25-4777-b324-dff105da705b@linux.alibaba.com> (raw)
In-Reply-To: <20240104092427.18119-1-zhangyongzhen@kylinos.cn>
On 1/4/24 5:24 PM, Yongzhen Zhang wrote:
> Modify reques to request in the comment
>
> Fixes: b1b1e15ef6b8 ("ocfs2: NFS hangs in __ocfs2_cluster_lock due to race with ocfs2_unblock_lock")
Since it's just a typo, I don't think it deserves a 'Fixes' tag.
> Signed-off-by: Yongzhen Zhang <zhangyongzhen@kylinos.cn>
> ---
> fs/ocfs2/dlmglue.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ocfs2/dlmglue.c b/fs/ocfs2/dlmglue.c
> index 64a6ef638495..cb40cafbc062 100644
> --- a/fs/ocfs2/dlmglue.c
> +++ b/fs/ocfs2/dlmglue.c
> @@ -1615,7 +1615,7 @@ static int __ocfs2_cluster_lock(struct ocfs2_super *osb,
> unlock:
> lockres_clear_flags(lockres, OCFS2_LOCK_UPCONVERT_FINISHING);
>
> - /* ocfs2_unblock_lock reques on seeing OCFS2_LOCK_UPCONVERT_FINISHING */
> + /* ocfs2_unblock_lock request on seeing OCFS2_LOCK_UPCONVERT_FINISHING */
> kick_dc = (lockres->l_flags & OCFS2_LOCK_BLOCKED);
>
> spin_unlock_irqrestore(&lockres->l_lock, flags);
next prev parent reply other threads:[~2024-01-06 1:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 9:24 [PATCH] ocfs2: Spelling fix Yongzhen Zhang
2024-01-06 1:55 ` Joseph Qi [this message]
2024-01-08 1:56 ` [PATCH v2] " Yongzhen Zhang
2024-01-08 2:21 ` Joseph Qi
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=64d54843-4e25-4777-b324-dff105da705b@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=zhangyongzhen@kylinos.cn \
/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