mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Necip Fazil Yildiran <fazilyildiran@gmail.com>
To: sagi@grimberg.me
Cc: minwoo.im.dev@gmail.com, kbusch@kernel.org, axboe@fb.com,
	hch@lst.de, linux-nvme@lists.infradead.org,
	linux-kernel@vger.kernel.org, paul@pgazz.com, jeho@cs.utexas.edu,
	Necip Fazil Yildiran <fazilyildiran@gmail.com>
Subject: [PATCH] nvme: tcp: fix kconfig dependency warning when !CRYPTO
Date: Mon, 14 Sep 2020 18:01:21 +0300	[thread overview]
Message-ID: <20200914150120.449602-1-fazilyildiran@gmail.com> (raw)

When NVME_TCP is enabled and CRYPTO is disabled, it results in the
following Kbuild warning:

WARNING: unmet direct dependencies detected for CRYPTO_CRC32C
  Depends on [n]: CRYPTO [=n]
  Selected by [y]:
  - NVME_TCP [=y] && INET [=y] && BLK_DEV_NVME [=y]

The reason is that NVME_TCP selects CRYPTO_CRC32C without depending on or
selecting CRYPTO while CRYPTO_CRC32C is subordinate to CRYPTO.

Honor the kconfig menu hierarchy to remove kconfig dependency warnings.

Fixes: 79fd751d61aa ("nvme: tcp: selects CRYPTO_CRC32C for nvme-tcp")
Signed-off-by: Necip Fazil Yildiran <fazilyildiran@gmail.com>
---
 drivers/nvme/host/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/nvme/host/Kconfig b/drivers/nvme/host/Kconfig
index 3ed9786b88d8..a44d49d63968 100644
--- a/drivers/nvme/host/Kconfig
+++ b/drivers/nvme/host/Kconfig
@@ -73,6 +73,7 @@ config NVME_TCP
 	depends on INET
 	depends on BLK_DEV_NVME
 	select NVME_FABRICS
+	select CRYPTO
 	select CRYPTO_CRC32C
 	help
 	  This provides support for the NVMe over Fabrics protocol using
-- 
2.25.1


             reply	other threads:[~2020-09-14 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 15:01 Necip Fazil Yildiran [this message]
2020-09-14 19:24 ` Sagi Grimberg
2020-09-15  5:59 ` 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=20200914150120.449602-1-fazilyildiran@gmail.com \
    --to=fazilyildiran@gmail.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=jeho@cs.utexas.edu \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=minwoo.im.dev@gmail.com \
    --cc=paul@pgazz.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®