Skip to contentSkip to conversation

Update target repo for nvme patch contributions

PATCH New Jay Freyensee 4 participants 6 messages Oct 16, 2015 – Oct 28, 2015 NVMe

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Update target repo for nvme patch contributions

Per http://www.nvmexpress.org/resources/linux-driver-information/, the old nvme git repo is stale. Updating MAINTAINERS to the Supported target currently used by the community.

Signed-off-by Jay Freyensee <james_p_freyensee at linux.intel.com>
Reviewed-by Christoph Hellwig <hch at lst.de>
---
 MAINTAINERS | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
MAINTAINERS +2 -1
index 601d766..578563b 100644
@@ -7441,7 +7441,8 @@ F:	drivers/video/fbdev/nvidia/
 NVM EXPRESS DRIVER
 M:	Matthew Wilcox <willy at linux.intel.com>
 L:	linux-nvme at lists.infradead.org
-T:	git git://git.infradead.org/users/willy/linux-nvme.git
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
+W:	https://kernel.googlesource.com/pub/scm/linux/kernel/git/axboe/linux-block/
 S:	Supported
 F:	drivers/nvme/host/
 F:	include/linux/nvme.h
Signature · 1 line
2.4.3
#1 lore raw

PATCH 1/1 Update target repo for nvme patch contributions

Since willy has taken a spectator role on linux-nvme in favor of new storage developments, it seems prudent to set the tree to a more active one.

This is not in drivers/block anymore, so question to Jens: do you want to take on maintenance for driver/nvme? We've been doing it this way de-facto for the past year, so if you're okay with listing your tree for nvme, that's definitely okay with me too.

I'll just throw out for the next merge window that I'm happy to herd all the nvme patches out there into a pull request in a public tree if that would help.

I've started this one, so far just with Christoph's latest, plus a fix from me from the fallout:

http://git.infradead.org/users/kbusch/linux-nvme.git

I'll be happy to add patches from other developers that appear to have been left behind as well.

Quoted 24 lines · Jay Freyensee

Per http://www.nvmexpress.org/resources/linux-driver-information/, the old nvme git repo is stale. Updating MAINTAINERS to the Supported target currently used by the community.

Signed-off-by Jay Freyensee <james_p_freyensee at linux.intel.com>
Reviewed-by Christoph Hellwig <hch at lst.de>
---
 MAINTAINERS | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
MAINTAINERS +2 -1
index 601d766..578563b 100644
@@ -7441,7 +7441,8 @@ F:	drivers/video/fbdev/nvidia/
 NVM EXPRESS DRIVER
 M:	Matthew Wilcox <willy at linux.intel.com>
 L:	linux-nvme at lists.infradead.org
-T:	git git://git.infradead.org/users/willy/linux-nvme.git
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
+W:	https://kernel.googlesource.com/pub/scm/linux/kernel/git/axboe/linux-block/
 S:	Supported
 F:	drivers/nvme/host/
 F:	include/linux/nvme.h
#2 lore raw

PATCH 1/1 Update target repo for nvme patch contributions

Quoted 13 lines · Keith

Since willy has taken a spectator role on linux-nvme in favor of new storage developments, it seems prudent to set the tree to a more active one.

This is not in drivers/block anymore, so question to Jens: do you want to take on maintenance for driver/nvme? We've been doing it this way de-facto for the past year, so if you're okay with listing your tree for nvme, that's definitely okay with me too.

I'll just throw out for the next merge window that I'm happy to herd all the nvme patches out there into a pull request in a public tree if that would help.

Quoted 7 lines

I've started this one, so far just with Christoph's latest, plus a fix from me from the fallout:

https://urldefense.proofpoint.com/v2/url?u=http-3A__git.infradead.org_users_kbusch_linux-2Dnvme.git&d=BQIBAg&c=5VD0RTtNlTh3ycd41b3MUw&r=cK1a7KivzZRh1fKQMjSm2A&m=aICLTTOdCBTmG8HlMbNQ5wFPxDvDGNR6EObxM8q3NJo&s=hNfXdogGq_cC562SAYK73S7g_kH2BJMuzIJwN1OZsp4&e=

I'll be happy to add patches from other developers that appear to have been left behind as well.

I'm fine with taking on a more official role, if you sign up with me. I could do a separate nvme branch/tree as well, or we could just keep folding into for-xx/drivers like we've been doing the last year.

Signature · 1 line
Jens Axboe
#3 lore raw

PATCH 1/1 Update target repo for nvme patch contributions

In reply to Busch, Keith
Quoted 9 lines · Keith

This is not in drivers/block anymore, so question to Jens: do you want to take on maintenance for driver/nvme? We've been doing it this way de-facto for the past year, so if you're okay with listing your tree for nvme, that's definitely okay with me too.

I'll just throw out for the next merge window that I'm happy to herd all the nvme patches out there into a pull request in a public tree if that would help.

Quoted 7 lines

I've started this one, so far just with Christoph's latest, plus a fix from me from the fallout:

http://git.infradead.org/users/kbusch/linux-nvme.git

I'll be happy to add patches from other developers that appear to have been left behind as well.

A nvme tree sounds useful to me, and I'd love to see you handle it.

But for now I think it might be a good idea if it gets pulled by Jens into the block layer tree given that nvme is driving a lot of the block layer work and having both merged early is going to make everyones life a lot easier.

#4 lore raw

PATCH 1/1 Update target repo for nvme patch contributions

Quoted 25 lines · Christoph Hellwig
Quoted 18 lines · Keith

This is not in drivers/block anymore, so question to Jens: do you want
to take on maintenance for driver/nvme? We've been doing it this way
de-facto for the past year, so if you're okay with listing your tree
for nvme, that's definitely okay with me too.

I'll just throw out for the next merge window that I'm happy to herd all
the nvme patches out there into a pull request in a public tree if that
would help.

I've started this one, so far just with Christoph's latest, plus a fix
from me from the fallout:

Quoted 5 lines

http://git.infradead.org/users/kbusch/linux-nvme.git

I'll be happy to add patches from other developers that appear to have
been left behind as well.

Quoted 8 lines

A nvme tree sounds useful to me, and I'd love to see you handle it.

But for now I think it might be a good idea if it gets pulled by Jens into the block layer tree given that nvme is driving a lot of the block
layer work and having both merged early is going to make everyones life
a lot easier.

Let me know if there is a different target or other info you'd like me to add to this patch and I'll change it.

#5 lore raw

PATCH 1/1 Update target repo for nvme patch contributions

Quoted 35 lines · J Freyensee
Quoted 25 lines · Christoph Hellwig
Quoted 18 lines · Keith

This is not in drivers/block anymore, so question to Jens: do you want
to take on maintenance for driver/nvme? We've been doing it this way
de-facto for the past year, so if you're okay with listing your tree
for nvme, that's definitely okay with me too.

I'll just throw out for the next merge window that I'm happy to herd all
the nvme patches out there into a pull request in a public tree if that
would help.

I've started this one, so far just with Christoph's latest, plus a fix
from me from the fallout:

Quoted 5 lines

https://urldefense.proofpoint.com/v2/url?u=http-3A__git.infradead.org_users_kbusch_linux-2Dnvme.git&d=CwICaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=cK1a7KivzZRh1fKQMjSm2A&m=3AfOrn0ifjKoR8xsyCHph2U_vW-xG3azjYonUOj09Mg&s=NARqRAFtEV9htXna-eRgE0NfEEDmWuf-G6vG_rkkKf8&e=

I'll be happy to add patches from other developers that appear to have
been left behind as well.

Quoted 8 lines

A nvme tree sounds useful to me, and I'd love to see you handle it.

But for now I think it might be a good idea if it gets pulled by Jens into the block layer tree given that nvme is driving a lot of the block
layer work and having both merged early is going to make everyones life
a lot easier.

Quoted 2 lines

Let me know if there is a different target or other info you'd like me to add to this patch and I'll change it.

I added your patch, and made the maintainer changes as well. As Christoph said, keeping it in the block tree for now will make life easier in the near future, as there will be dependency changes between blk-mq and nvme. We can always change this later, if there's a need or desire for that.

Signature · 1 line
Jens Axboe