From mboxrd@z Thu Jan  1 00:00:00 1970
From: keith.busch@intel.com (Keith Busch)
Date: Wed, 11 Mar 2015 18:40:20 +0000 (UTC)
Subject: NVMe driver status
In-Reply-To: <BN1PR0401MB093160344D56E4DE445069D3F2190@BN1PR0401MB0931.namprd04.prod.outlook.com>
References: <004b01d033df$9d6c2be0$d84483a0$@samsung.com>
 <alpine.LNX.2.00.1501191414000.15481@localhost.lm.intel.com>
 <000d01d034a8$fa00f060$ee02d120$@samsung.com>
 <alpine.LNX.2.00.1501201537470.15481@localhost.lm.intel.com>
 <002501d05b45$cbc9b790$635d26b0$@samsung.com>
 <BN3PR0401MB144453DABCDC7F809E4DE017FD180@BN3PR0401MB1444.namprd04.prod.outlook.com>
 <alpine.LNX.2.00.1503101947270.32385@localhost.lm.intel.com>
 <BN1PR0401MB093160344D56E4DE445069D3F2190@BN1PR0401MB0931.namprd04.prod.outlook.com>
Message-ID: <alpine.LNX.2.00.1503111827090.32385@localhost.lm.intel.com>

On Wed, 11 Mar 2015, Brandon Schulz wrote:
> Is there any kind of coordination among contributors on backports to
> legacy-nvme or is it just kind of a free-for-all until someone submits a
> patch on this list?

Coordination is done on the mailing lists, though that probably feels
a bit like a free-for-all.

I originally started the 3.18 fork so I can point distro vendors using
older kernels to a public tree to pull commits ahead of their updates. It
sounds like there is considerable outside interest, so if people are open
to co-maintaining, we can fork this to a github or something like that.

> Thanks,
> Brandon