From: Sagi Grimberg <sagi@grimberg.me>
To: Hannes Reinecke <hare@suse.de>,
"Belanger, Martin" <Martin.Belanger@dell.com>,
Martin Belanger <nitram_67@hotmail.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@fb.com" <axboe@fb.com>, "hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH 3/4] nvme-fabrics: add tp8010 support
Date: Sun, 30 Jan 2022 15:18:13 +0200 [thread overview]
Message-ID: <15725ffe-d706-9723-de5a-d0d247859c84@grimberg.me> (raw)
In-Reply-To: <13c327cf-8f04-e005-298f-0e43bb39b89e@grimberg.me>
> Yes, thgere is no bdev for discovery controllers. We may add a uevent
> for userspace to consume as soon as the transport reconnects or when
> a controller (re)starts.
Something like this should be sufficient:
--
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index dd18861f77c0..55e11ee19460 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -4396,6 +4396,7 @@ void nvme_start_ctrl(struct nvme_ctrl *ctrl)
nvme_queue_scan(ctrl);
nvme_start_queues(ctrl);
}
+ kobject_uevent(&ctrl->device->kobj, KOBJ_ONLINE);
}
EXPORT_SYMBOL_GPL(nvme_start_ctrl);
--
next prev parent reply other threads:[~2022-01-30 13:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220125145956.14746-1-nitram_67@hotmail.com>
2022-01-25 14:59 ` [PATCH 1/4] nvme-fabrics: add discovery controller type Martin Belanger
2022-01-27 9:16 ` Hannes Reinecke
2022-01-27 13:37 ` Belanger, Martin
2022-01-27 13:16 ` Sagi Grimberg
2022-01-25 14:59 ` [PATCH 2/4] nvme: add host symbolic name Martin Belanger
2022-01-27 9:18 ` Hannes Reinecke
2022-01-27 13:20 ` Sagi Grimberg
2022-01-25 14:59 ` [PATCH 3/4] nvme-fabrics: add tp8010 support Martin Belanger
2022-01-27 9:30 ` Hannes Reinecke
2022-01-27 13:12 ` Sagi Grimberg
2022-01-27 13:30 ` Belanger, Martin
2022-01-27 14:28 ` Hannes Reinecke
2022-01-27 21:59 ` Sagi Grimberg
2022-01-28 17:55 ` Belanger, Martin
2022-01-28 21:49 ` Hannes Reinecke
2022-01-28 23:02 ` Belanger, Martin
2022-01-29 8:43 ` Hannes Reinecke
2022-01-29 12:23 ` Belanger, Martin
2022-01-29 12:47 ` Hannes Reinecke
2022-01-30 8:46 ` Sagi Grimberg
2022-01-30 13:18 ` Sagi Grimberg [this message]
2022-01-31 12:08 ` Belanger, Martin
2022-01-31 16:05 ` Sagi Grimberg
2022-01-31 16:16 ` Belanger, Martin
2022-01-31 18:56 ` Sagi Grimberg
2022-02-02 8:36 ` Hannes Reinecke
2022-01-31 17:03 ` John Meneghini
2022-01-31 17:17 ` Belanger, Martin
2022-01-31 18:28 ` John Meneghini
2022-01-25 14:59 ` [PATCH 4/4] nvme-fabrics: add explicit deregistration on disconnect Martin Belanger
2022-01-27 9:31 ` Hannes Reinecke
2022-01-27 13:14 ` 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=15725ffe-d706-9723-de5a-d0d247859c84@grimberg.me \
--to=sagi@grimberg.me \
--cc=Martin.Belanger@dell.com \
--cc=axboe@fb.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nitram_67@hotmail.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.