From: hch@infradead.org (Christoph Hellwig)
Subject: Bug Report: can't unload nvme module in case of disabled device
Date: Thu, 10 Aug 2017 01:59:50 -0700 [thread overview]
Message-ID: <20170810085950.GB12494@infradead.org> (raw)
In-Reply-To: <f28ebc80-0e67-8af7-79b2-a4b368e4bd83@mellanox.com>
Is this a PCIe or fabrics controller? Did you get a chance to bisect
where this behavior appeared?
next prev parent reply other threads:[~2017-08-10 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 12:58 Bug Report: can't unload nvme module in case of disabled device Max Gurtovoy
2017-08-10 8:59 ` Christoph Hellwig [this message]
2017-08-10 17:04 ` Max Gurtovoy
2017-08-10 19:36 ` Keith Busch
2017-08-13 8:29 ` Max Gurtovoy
2017-08-14 20:24 ` Keith Busch
2017-08-10 16:45 ` Keith Busch
2017-08-10 19:17 ` Keith Busch
2017-08-10 19:34 ` Keith Busch
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=20170810085950.GB12494@infradead.org \
--to=hch@infradead.org \
/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