From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <keith.busch@wdc.com>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCHv2] nvme: generate uevent once a multipath namespace is operational again
Date: Wed, 12 May 2021 08:20:47 +0200 [thread overview]
Message-ID: <20210512062047.GA18271@lst.de> (raw)
In-Reply-To: <7b01589e-3987-9573-ccd7-b599affed2a5@suse.de>
On Wed, May 12, 2021 at 07:24:44AM +0200, Hannes Reinecke wrote:
>> Can you please also add a comment why we are sending the event?
>>
> You mean, why sending KOBJ_CHANGE and not KOBJ_ADD?
Maybe that to, but most importantly why we are sending an event here.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-05-12 6:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 8:03 [PATCHv2] nvme: generate uevent once a multipath namespace is operational again Hannes Reinecke
2021-05-11 16:19 ` Christoph Hellwig
2021-05-12 5:24 ` Hannes Reinecke
2021-05-12 6:20 ` Christoph Hellwig [this message]
2021-05-12 13:06 ` Hannes Reinecke
2021-05-11 17:08 ` 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=20210512062047.GA18271@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=keith.busch@wdc.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.