From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme-fc: use pci device as parent for nvme controller
Date: Sat, 19 Jan 2019 14:08:10 +0100 [thread overview]
Message-ID: <20190119130810.GA24374@lst.de> (raw)
In-Reply-To: <20190117074241.40672-1-hare@suse.de>
On Thu, Jan 17, 2019@08:42:41AM +0100, Hannes Reinecke wrote:
> To allow system tools to figure out which pci device provides a
> given NVMe controller this patch moves the nvme controller sysfs
> entry as a child of the PCI device.
>
> With this tools like dracut can traverse the device hierarchy to figure
> out which modules to include.
Doesn't ->create_ctrl consumer the reference to the passed in device,
or in other words you create a leak on the fabrics device here?
next prev parent reply other threads:[~2019-01-19 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 7:42 [PATCH] nvme-fc: use pci device as parent for nvme controller Hannes Reinecke
2019-01-19 13:08 ` Christoph Hellwig [this message]
2019-01-21 13:57 ` Hannes Reinecke
2019-01-20 16:38 ` James Smart
2019-01-23 7:42 ` Christoph Hellwig
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=20190119130810.GA24374@lst.de \
--to=hch@lst.de \
/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