Linux NFS development
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Sun Ke <sunke32@huawei.com>
Cc: trond.myklebust@hammerspace.com, anna@kernel.org,
	linux-nfs@vger.kernel.org, kernel-janitors@vger.kernel.org,
	neilb@suse.de
Subject: Re: [PATCH] NFS: Fix missing unlock in nfs_unlink()
Date: Tue, 16 Aug 2022 11:28:13 +0300	[thread overview]
Message-ID: <20220816082813.GR3438@kadam> (raw)
In-Reply-To: <5e947976-0808-1d32-e170-d85ef73972e7@huawei.com>

On Tue, Aug 16, 2022 at 09:06:06AM +0800, Sun Ke wrote:
> friendly ping...
> 
> 在 2022/8/12 9:14, Sun Ke 写道:
> > Add the missing unlock before goto.


The patch is correct, but please wait at least two weeks before sending
reminders.  Longer than two weeks if the merge window is open.

regards,
dan carpenter


  reply	other threads:[~2022-08-16 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12  1:14 [PATCH] NFS: Fix missing unlock in nfs_unlink() Sun Ke
2022-08-16  1:06 ` Sun Ke
2022-08-16  8:28   ` Dan Carpenter [this message]
2022-08-17  1:50     ` Sun Ke

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=20220816082813.GR3438@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=anna@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=sunke32@huawei.com \
    --cc=trond.myklebust@hammerspace.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