From: keith.busch@intel.com (Keith Busch)
Subject: [RFC PATCH] nvme: Submit uevents for log page notification
Date: Wed, 14 Jun 2017 11:42:14 -0400 [thread overview]
Message-ID: <20170614154213.GE26073@localhost.localdomain> (raw)
In-Reply-To: <20170614150546.GA32323@infradead.org>
On Wed, Jun 14, 2017@08:05:46AM -0700, Christoph Hellwig wrote:
> Given that we have the uevent discussion again can you resubmit this
> with the comments address, most notably only enabling it for the
> uevents we want userspace to handle. Maybe including whatever
> code you have on the userspace side (even if it's an ugly prototype)
Thanks for reminding me. I'll rebase, address the comments, and resend
shortly.
next prev parent reply other threads:[~2017-06-14 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 20:49 [RFC PATCH] nvme: Submit uevents for log page notification Keith Busch
2017-03-30 8:36 ` Christoph Hellwig
2017-06-14 15:05 ` Christoph Hellwig
2017-06-14 15:42 ` Keith Busch [this message]
2017-06-15 9:41 ` Sagi Grimberg
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=20170614154213.GE26073@localhost.localdomain \
--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 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.