[PATCH] Update target repo for nvme patch contributions

[PATCH] Update target repo for nvme patch contributions

[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(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 601d766..578563b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -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.4.3

[PATCH] Update target repo for nvme patch contributions

[Busch, 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.

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.

On Fri, Oct 16, 2015@10:48:31AM -0700, Jay Freyensee wrote:
> 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(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 601d766..578563b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -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

[PATCH] Update target repo for nvme patch contributions

[Jens Axboe]

On 10/16/2015 05:47 PM, Busch, Keith wrote:
> 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:
>
>    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.

-- 
Jens Axboe

[PATCH] Update target repo for nvme patch contributions

[Christoph Hellwig]

On Fri, Oct 16, 2015@11:47:01PM +0000, Busch, Keith wrote:
> 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.

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.

[PATCH] Update target repo for nvme patch contributions

[J Freyensee]

On Sun, 2015-10-18@20:23 +0200, Christoph Hellwig wrote:
> On Fri, Oct 16, 2015@11:47:01PM +0000, Busch, Keith wrote:
> > 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.
> 
> 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.

[PATCH] Update target repo for nvme patch contributions

[Jens Axboe]

On 10/21/2015 02:38 AM, J Freyensee wrote:
> On Sun, 2015-10-18@20:23 +0200, Christoph Hellwig wrote:
>> On Fri, Oct 16, 2015@11:47:01PM +0000, Busch, Keith wrote:
>>> 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:
>>>
>>>    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.
>>
>> 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.

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.

-- 
Jens Axboe