From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Jens Axboe <axboe@kernel.dk>,
dlemoal@kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH v2 1/1] null_blk: Fix the problem "mutex_destroy missing"
Date: Thu, 25 Apr 2024 19:11:59 +0200 [thread overview]
Message-ID: <52a728e6-deef-4670-b987-435296b42047@linux.dev> (raw)
In-Reply-To: <e69bea72-1454-46ea-82f6-c1d091ba8a58@kernel.dk>
OK. V3 is on the way.
Zhu Yanjun
在 2024/4/25 19:11, Jens Axboe 写道:
> On 4/25/24 11:01 AM, Zhu Yanjun wrote:
>> When a mutex lock is not used any more, the function mutex_destroy
>> should be called to mark the mutex lock uninitialized.
> You didn't fix the title...
>
--
I only represent myself.
prev parent reply other threads:[~2024-04-25 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 17:01 [PATCH v2 1/1] null_blk: Fix the problem "mutex_destroy missing" Zhu Yanjun
2024-04-25 17:11 ` Jens Axboe
2024-04-25 17:11 ` Zhu Yanjun [this message]
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=52a728e6-deef-4670-b987-435296b42047@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=linux-block@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.