Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: NVMe driver status
Date: Tue, 10 Mar 2015 20:01:40 +0000 (UTC)	[thread overview]
Message-ID: <alpine.LNX.2.00.1503101947270.32385@localhost.lm.intel.com> (raw)
In-Reply-To: <BN3PR0401MB144453DABCDC7F809E4DE017FD180@BN3PR0401MB1444.namprd04.prod.outlook.com>

I'm happy to apply requested changes. I can't necessarily guarantee a
particular deadline, though I try to align with interested OS vendors
ahead of their release updates if they're using the older version.

Specifically on async probe and others, I'll get these merged in later
this week.

On Tue, 10 Mar 2015, David Darrington wrote:
> I'm interested in this also. I know that the there is a quarterly planning call for the ofed Windows NVMe driver. Would there be any interest in having occasional conference calls to discuss items such as these? I would be glad to setup a call, as long as Keith and/or Mathew agree that it is worthwhile and can attend.
>
> -----Original Message-----
> From: Linux-nvme [mailto:linux-nvme-bounces at lists.infradead.org] On Behalf Of Sunad Bhandary
> Sent: Tuesday, March 10, 2015 10:21 AM
> To: 'Keith Busch'
> Cc: linux-nvme at lists.infradead.org
> Subject: RE: NVMe driver status
>
> Hi Keith,
> Can we initiate some activity on the legacy-nvme maintenance?
>
> Can you commit the async controller probe patch for the legacy driver also?
> Or I can do this if you want.
> Also, I'll be submitting the legacy-nvme version for a couple of patches that we already submitted (write_long, split i/o in IOCtl path).
>
> Going forward, how will the legacy-nvme be maintained?
> The legacy-nvme was removed in 3.19. So are we going to have some restrictions on the kernel versions supported by legacy nvme driver

  reply	other threads:[~2015-03-10 20:01 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 [this message]
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

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.1503101947270.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