[PATCH 0/6] Six NVMeOF-related patches

Sagi Grimberg sagi at grimberg.me
Fri Oct 21 14:33:39 PDT 2016

>> Maybe.  Or we should just add Sagi and me to the general NVMe antry
>> and replace the Fabrics git tree with a general NVMe one.
>> Keith, Jens - any preferences?
> I've no preference. I assumed, though, fabrics developers/users found
> the public staging tree useful since it seems to be changing faster
> than the rest of the driver.


However this tree is designed to share the load with Jens so he doesn't
need to closely monitor all the fabrics changes. IMO It worked pretty
well for the inclusion process and 4.8-rc fixes.

I was a bit busy lately but wanted to pick up on 4.9-rc and 4.10 related
stuff next week.

> We don't have an nvme specific tree, so
> if everyone's okay going through the general block, then let's add the
> maintainer entries.

It all goes through Jens, I think Christoph was offering to increase the
scope of the nvmf tree to nvme in general. This way, you, Christoph and
me can offload from Jens some nvme related patch traffic and send him
pull requests. But if you are more comfortable with the way things are
we can leave it as is.

More information about the Linux-nvme mailing list