From: keith.busch@intel.com (Keith Busch)
Subject: [PATCHv2] NVMe: Async event request
Date: Wed, 18 Jun 2014 11:38:48 -0600 (MDT) [thread overview]
Message-ID: <alpine.LRH.2.03.1406181138180.4699@AMR> (raw)
In-Reply-To: <1403109380-12247-1-git-send-email-keith.busch@intel.com>
Scratch this ... it loses count on a suspend/resume or reset.
On Wed, 18 Jun 2014, Keith Busch wrote:
> Submits NVMe asynchronous event requests, one event up to the controller
> maximum or number of possible different event types (8), whichever is
> smaller. Events successfully returned by the controller are logged.
>
> Signed-off-by: Keith Busch <keith.busch at intel.com>
next prev parent reply other threads:[~2014-06-18 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 16:36 [PATCHv2] NVMe: Async event request Keith Busch
2014-06-18 17:38 ` Keith Busch [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-19 18:13 Keith Busch
2013-07-19 20:41 ` Matthew Wilcox
2013-07-22 15:00 ` Busch, Keith
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.LRH.2.03.1406181138180.4699@AMR \
--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