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

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

 



Sure, should I have it on top of the affinity patches or not?

For now get any tree you have out to take a look.  In the longer
run we'll need to decide how we want to deal with the merge
of the two trees.  In general having to depend on the RDMA
tree is a major risk because it's maintainance is so unreliable.

Its really a small conflict, easy enough to get it without. The problem
that no matter what I do, one tree would conflict...

If it's in a branch of its own we could pull it in through and
send that bit through both trees.

We can do that, should I use the nvme tree for that? or maybe once we
converge on the patch set?



[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