From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH v2 3/3] nvme: fire discovery log page change events to userspace
Date: Sun, 14 Jul 2019 17:14:56 +0900 [thread overview]
Message-ID: <20190714081456.GD2993@minwoo-desktop> (raw)
In-Reply-To: <20190712180211.26333-4-sagi@grimberg.me>
On 19-07-12 11:02:11, Sagi Grimberg wrote:
> Provide userspace with nvme discovery controller device instance,
> controller traddr and trsvcid. We'd expect userspace to handle
> this event by issuing a discovery + connect.
>
> Signed-off-by: Sagi Grimberg <sagi at grimberg.me>
Sagi, Thanks for this patch!
Reviewed-by: Minwoo Im <minwoo.im.dev at gmail.com>
next prev parent reply other threads:[~2019-07-14 8:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 18:02 [PATCH v2 0/3] Support discovery log change events Sagi Grimberg
2019-07-12 18:02 ` [PATCH v2 1/3] nvme-fabrics: allow discovery subsystems accept a kato Sagi Grimberg
2019-07-14 8:08 ` Minwoo Im
2019-07-14 15:00 ` James Smart
2019-07-19 13:48 ` Hannes Reinecke
2019-07-12 18:02 ` [PATCH v2 2/3] nvme: enable aen also for discovery controllers Sagi Grimberg
2019-07-14 8:09 ` Minwoo Im
2019-07-14 15:04 ` James Smart
2019-07-19 13:49 ` Hannes Reinecke
2019-07-12 18:02 ` [PATCH v2 3/3] nvme: fire discovery log page change events to userspace Sagi Grimberg
2019-07-14 8:14 ` Minwoo Im [this message]
2019-07-14 15:13 ` James Smart
2019-07-19 13:49 ` Hannes Reinecke
[not found] ` <20190822002328.GP9511@lst.de>
[not found] ` <205d06ab-fedc-739d-323f-b358aff2cbfe@grimberg.me>
[not found] ` <e4603511-6dae-e26d-12a9-e9fa727a8d03@grimberg.me>
2019-08-26 6:56 ` Christoph Hellwig
2019-08-26 7:59 ` Greg Kroah-Hartman
2019-08-29 18:21 ` Sagi Grimberg
2019-08-30 5:55 ` Christoph Hellwig
2019-08-30 18:08 ` Sagi Grimberg
2019-08-30 18:08 ` Sagi Grimberg
2019-08-30 18:36 ` James Smart
2019-08-30 18:36 ` James Smart
2019-08-30 21:07 ` Sagi Grimberg
2019-08-30 21:07 ` Sagi Grimberg
2019-08-30 22:24 ` James Smart
2019-08-30 22:24 ` James Smart
2019-09-09 15:10 ` Hannes Reinecke
2019-09-09 15:10 ` Hannes Reinecke
2019-08-30 6:20 ` Greg Kroah-Hartman
2019-08-30 18:14 ` Sagi Grimberg
2019-08-30 18:14 ` Sagi Grimberg
2019-09-02 19:33 ` Greg Kroah-Hartman
2019-09-02 19:33 ` Greg Kroah-Hartman
2019-09-04 1:35 ` Sagi Grimberg
2019-09-04 1:35 ` Sagi Grimberg
2019-09-04 5:25 ` Greg Kroah-Hartman
2019-09-04 5:25 ` Greg Kroah-Hartman
2019-08-01 1:32 ` [PATCH v2 0/3] Support discovery log change events 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=20190714081456.GD2993@minwoo-desktop \
--to=minwoo.im.dev@gmail.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.