linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: Ye Bin <yebin10@huawei.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
	nbd@other.debian.org, linux-kernel@vger.kernel.org,
	yukuai3@huawei.com
Subject: Re: [PATCH -next v3 0/2] Fix hungtask when nbd_config_put
Date: Mon, 1 Nov 2021 18:27:32 -0400	[thread overview]
Message-ID: <YYBp1LO83KWlov7V@localhost.localdomain> (raw)
In-Reply-To: <20211101062956.791573-1-yebin10@huawei.com>

On Mon, Nov 01, 2021 at 02:29:54PM +0800, Ye Bin wrote:
> Ye Bin (2):
>   nbd: Fix incorrect error handle when first_minor big than '0xff' in
>     nbd_dev_add
>   nbd: Fix hungtask when nbd_config_put
> 
>  drivers/block/nbd.c | 36 ++++++++++++++++--------------------
>  1 file changed, 16 insertions(+), 20 deletions(-)
> 

Hmm this seems to overlap with the series

https://lore.kernel.org/linux-block/20211021122936.758221-1-yukuai3@huawei.com/

and they are different checks, can y'all work out what this is supposed to look
like and send one series to integrate both sets of fixes?  Thanks,

Josef

  parent reply	other threads:[~2021-11-01 22:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01  6:29 [PATCH -next v3 0/2] Fix hungtask when nbd_config_put Ye Bin
2021-11-01  6:29 ` [PATCH -next v3 1/2] nbd: Fix incorrect error handle when first_minor big than '0xff' in nbd_dev_add Ye Bin
2021-11-01  6:29 ` [PATCH -next v3 2/2] nbd: Fix hungtask when nbd_config_put Ye Bin
2021-11-01 22:27 ` Josef Bacik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-29  9:42 [PATCH -next v3 0/2] " Ye Bin

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=YYBp1LO83KWlov7V@localhost.localdomain \
    --to=josef@toxicpanda.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbd@other.debian.org \
    --cc=yebin10@huawei.com \
    --cc=yukuai3@huawei.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;
as well as URLs for NNTP newsgroup(s).