From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH rfc] nvme-fabrics: request transport module
Date: Sun, 24 Sep 2017 15:04:46 +0200 [thread overview]
Message-ID: <20170924130446.GA7373@lst.de> (raw)
In-Reply-To: <74246ccf-53e3-7956-3117-16e44f2f8793@grimberg.me>
On Sun, Sep 24, 2017@04:03:55PM +0300, Sagi Grimberg wrote:
>> Also if I remember correctly request_module returns an error if the
>> driver is built-in, thus most callers either don't check the return
>> value or just print a warning (I personally hate the warning, so I think
>> we should just do the simple request_module call).
>
> So skip the return value altogether? I don't mind that...
Yes.
prev parent reply other threads:[~2017-09-24 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 12:45 [PATCH rfc] nvme-fabrics: request transport module Sagi Grimberg
2017-09-24 12:55 ` Christoph Hellwig
2017-09-24 13:03 ` Sagi Grimberg
2017-09-24 13:04 ` Christoph Hellwig [this message]
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=20170924130446.GA7373@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 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.