linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: axboe@fb.com (Jens Axboe)
Subject: [PATCH] Update target repo for nvme patch contributions
Date: Sun, 18 Oct 2015 11:01:41 -0600	[thread overview]
Message-ID: <5623D075.1070708@fb.com> (raw)
In-Reply-To: <20151016234700.GA13234@localhost.localdomain>

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

  reply	other threads:[~2015-10-18 17:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 17:48 [PATCH] Update target repo for nvme patch contributions Jay Freyensee
2015-10-16 23:47 ` Busch, Keith
2015-10-18 17:01   ` Jens Axboe [this message]
2015-10-18 18:23   ` Christoph Hellwig
2015-10-20 17:38     ` J Freyensee
2015-10-28  7:40       ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5623D075.1070708@fb.com \
    --to=axboe@fb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).