Re: Centralize nvme controller reset, delete and fabrics periodic reconnects

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

To: Sagi Grimberg <sagi@xxxxxxxxxxx>
Subject: Re: Centralize nvme controller reset, delete and fabrics periodic reconnects
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 16 Aug 2017 01:16:05 -0700
Cc: linux-nvme@xxxxxxxxxxxxxxxxxxx, Christoph Hellwig <hch@xxxxxx>, Keith Busch <keith.busch@xxxxxxxxx>, linux-block@xxxxxxxxxxxxxxx
In-reply-to: <1502790745-12569-1-git-send-email-sagi@grimberg.me>
User-agent: Mutt/1.8.3 (2017-05-23)

> This set applies on nvme-4.14 plus 4.13 recent fixes.

I can't get this applied at all.  A pointer to a git repo would
always be nice for patchsets as large as this one, especially if
the base is a bit murky..

Follow-Ups:
- Re: Centralize nvme controller reset, delete and fabrics periodic reconnects
  - From: Sagi Grimberg

References:
- Centralize nvme controller reset, delete and fabrics periodic reconnects
  - From: Sagi Grimberg

Prev by Date: Re: [PATCH] blktrace: Fix potentail deadlock between delete & sysfs ops
Next by Date: migrate the block tests from Dimity to blktests?
Previous by thread: [PATCH 12/12] nvme-loop: convert to nvme-core control plane management
Next by thread: Re: Centralize nvme controller reset, delete and fabrics periodic reconnects
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