From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 1/3] nvme-fabrics: don't check for non-NULL module in nvmf_register_transport
Date: Thu, 22 Feb 2018 08:31:35 -0700 [thread overview]
Message-ID: <20180222153134.GF7076@localhost.localdomain> (raw)
In-Reply-To: <20180222152410.19222-2-hch@lst.de>
On Thu, Feb 22, 2018@07:24:08AM -0800, Christoph Hellwig wrote:
> THIS_MODULE evaluates to NULL when used from code built into the kernel,
> thus breaking built-in transport modules. Remove the bogus check.
>
> Fixes: 0de5cd36 ("nvme-fabrics: protect against module unload during create_ctrl")
> Signed-off-by: Christoph Hellwig <hch at lst.de>
Looks good.
Reviewed-by: Keith Busch <keith.busch at intel.com>
next prev parent reply other threads:[~2018-02-22 15:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 15:24 small fixes for 4.16 and -stable Christoph Hellwig
2018-02-22 15:24 ` [PATCH 1/3] nvme-fabrics: don't check for non-NULL module in nvmf_register_transport Christoph Hellwig
2018-02-22 15:31 ` Keith Busch [this message]
2018-02-22 15:34 ` Sagi Grimberg
2018-02-22 15:24 ` [PATCH 2/3] nvme-rdma: use blk_rq_payload_bytes instead of blk_rq_bytes Christoph Hellwig
2018-02-22 15:31 ` Keith Busch
2018-02-22 15:34 ` Sagi Grimberg
2018-02-22 15:39 ` Johannes Thumshirn
2018-02-22 15:58 ` Bart Van Assche
2018-02-22 15:24 ` [PATCH 3/3] nvmet-loop: use blk_rq_payload_bytes for sgl selection Christoph Hellwig
2018-02-22 15:32 ` Keith Busch
2018-02-22 15:34 ` Sagi Grimberg
2018-02-22 15:39 ` Johannes Thumshirn
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=20180222153134.GF7076@localhost.localdomain \
--to=keith.busch@intel.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.