All of lore.kernel.org
 help / color / mirror / Atom feed
From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH] Update target repo for nvme patch contributions
Date: Tue, 20 Oct 2015 10:38:38 -0700	[thread overview]
Message-ID: <1445362718.2819.40.camel@linux.intel.com> (raw)
In-Reply-To: <20151018182337.GB21211@lst.de>

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.

  reply	other threads:[~2015-10-20 17:38 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
2015-10-18 18:23   ` Christoph Hellwig
2015-10-20 17:38     ` J Freyensee [this message]
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=1445362718.2819.40.camel@linux.intel.com \
    --to=james_p_freyensee@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.