From: keith.busch@intel.com (Keith Busch)
Subject: NVMe driver status
Date: Mon, 16 Mar 2015 17:19:53 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1503161710060.32385@localhost.lm.intel.com> (raw)
In-Reply-To: <BN1PR0401MB0931D933261F248E7B278238F2020@BN1PR0401MB0931.namprd04.prod.outlook.com>
If you setup a github project, I'll subscribe to it.
I merged all the upstream patches I intended to apply today and pushed to
'for-next' branch in the nvme-legacy git tree. I haven't fully tested yet,
otherwise I'd have just merged to master.
Also merged the lastest stable 3.18.y to master.
On Mon, 16 Mar 2015, Brandon Schulz wrote:
> Keith -
>
> Any more thoughts on how we proceed with setting up this co-maintained Github space?
>
> Thanks,
> Brandon
prev parent reply other threads:[~2015-03-16 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 12:00 NVMe driver status Sunad Bhandary
2015-01-19 14:33 ` Keith Busch
2015-01-20 12:02 ` Sunad Bhandary
2015-01-20 15:46 ` Keith Busch
2015-03-10 15:20 ` Sunad Bhandary
2015-03-10 19:11 ` David Darrington
2015-03-10 20:01 ` Keith Busch
2015-03-11 18:06 ` Brandon Schulz
2015-03-11 18:40 ` Keith Busch
2015-03-11 21:17 ` Brandon Schulz
2015-03-12 2:01 ` Keith Busch
2015-03-12 16:32 ` Brandon Schulz
2015-03-16 14:52 ` Brandon Schulz
2015-03-16 17:19 ` Keith Busch [this message]
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=alpine.LNX.2.00.1503161710060.32385@localhost.lm.intel.com \
--to=keith.busch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox