mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: clabbe@baylibre.com, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org
Subject: [PATCH] crypto: ixp4xx - Remove COMPILE_TEST from Kconfig dependencies
Date: Fri, 07 Apr 2023 14:37:44 -0500	[thread overview]
Message-ID: <37694343f8b89dc0469d4a1718dad8f5f8c765bd.camel@linux.intel.com> (raw)

COMPILE_TEST was added during the move to drivers/crypto/intel/ but
shouldn't have been as it triggers a build bug when not compiled by
the target compiler.  So remove it to match the original.

Reported-by: kernel test robot <lkp@intel.com>
Link: https://lore.kernel.org/oe-kbuild-all/202304061846.G6cpPXiQ-lkp@intel.com/
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
---
 drivers/crypto/intel/ixp4xx/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/crypto/intel/ixp4xx/Kconfig b/drivers/crypto/intel/ixp4xx/Kconfig
index af3cc5688328..4cfb1e37f45b 100644
--- a/drivers/crypto/intel/ixp4xx/Kconfig
+++ b/drivers/crypto/intel/ixp4xx/Kconfig
@@ -1,6 +1,6 @@
 config CRYPTO_DEV_IXP4XX
 	tristate "Driver for IXP4xx crypto hardware acceleration"
-	depends on (ARCH_IXP4XX || COMPILE_TEST) && IXP4XX_QMGR && IXP4XX_NPE
+	depends on ARCH_IXP4XX && IXP4XX_QMGR && IXP4XX_NPE
 	select CRYPTO_AES
 	select CRYPTO_DES
 	select CRYPTO_ECB
-- 
2.34.1



             reply	other threads:[~2023-04-07 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 19:37 Tom Zanussi [this message]
2023-04-09  7:46 ` [PATCH] crypto: ixp4xx - Do not check word size when compile testing Herbert Xu
2023-04-13 20:12   ` Linus Walleij

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=37694343f8b89dc0469d4a1718dad8f5f8c765bd.camel@linux.intel.com \
    --to=tom.zanussi@linux.intel.com \
    --cc=clabbe@baylibre.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®