Re: [PATCHv4 0/4] block and nvme passthrough error handling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: linux-nvme@xxxxxxxxxxxxxxxxxxx, sagi@xxxxxxxxxxx, hch@xxxxxx, linux-block@xxxxxxxxxxxxxxx
Subject: Re: [PATCHv4 0/4] block and nvme passthrough error handling
From: Keith Busch <kbusch@xxxxxxxxxx>
Date: Tue, 22 Jun 2021 23:57:18 +0900
Cc: axboe@xxxxxxxxx, Yuanyuan Zhong <yzhong@xxxxxxxxxxxxxxx>, Casey Chen <cachen@xxxxxxxxxxxxxxx>, Ming Lei <ming.lei@xxxxxxxxxx>
In-reply-to: <20210610214437.641245-1-kbusch@kernel.org>
References: <20210610214437.641245-1-kbusch@kernel.org>
User-agent: Mutt/1.12.1 (2019-06-15)

Jens,

Do you have any thoughts on this series? I think it's good to go and
have received reviews, and just want to check if you are okay to take
this through block.

Thanks,
Keith

Follow-Ups:
- Re: [PATCHv4 0/4] block and nvme passthrough error handling
  - From: Jens Axboe

References:
- [PATCHv4 0/4] block and nvme passthrough error handling
  - From: Keith Busch

Prev by Date: Re: Re: [PATCH v3] virtio-blk: Add validation for block size in config space
Next by Date: Re: [PATCH v3 1/3] zram: fix crashes due to use of cpu hotplug multistate
Previous by thread: Re: [PATCHv4 4/4] nvme: use return value from blk_execute_rq()
Next by thread: Re: [PATCHv4 0/4] block and nvme passthrough error handling
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux