Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Pavitrakumar Managutte" <pavitrakumarm@vayavyalabs.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v13 4/4] crypto: spacc - Add SPAcc Kconfig and Makefile
Date: Thu, 04 Jun 2026 17:06:39 +0000	[thread overview]
Message-ID: <20260604170640.3CBC01F00898@smtp.kernel.org> (raw)
In-Reply-To: <20260604165210.1141842-5-pavitrakumarm@vayavyalabs.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The Kconfig symbol `CRYPTO_DEV_SPACC_HASH` selects a non-existent symbol `CRYPTO_MICHAEL_MIC`.
--

commit 5b42eeec08a6835428f268bf6ab818260b6818d2
Author: Pavitrakumar Managutte <pavitrakumarm@vayavyalabs.com>

crypto: spacc - Add SPAcc Kconfig and Makefile

This commit adds the Makefile and Kconfig definitions for the new dwc_spacc
Security Protocol Accelerator driver.

> diff --git a/drivers/crypto/dwc-spacc/Kconfig b/drivers/crypto/dwc-spacc/Kconfig
> new file mode 100644
> index 0000000000000..f9752e6f664b8
> --- /dev/null
> +++ b/drivers/crypto/dwc-spacc/Kconfig

[ ... ]

> +config CRYPTO_DEV_SPACC_HASH
> +	bool "Enable HASH functionality"
> +	depends on CRYPTO_DEV_SPACC
> +	default y
> +	select CRYPTO_HASH
> +	select CRYPTO_SHA1
> +	select CRYPTO_MD5
> +	select CRYPTO_SHA256
> +	select CRYPTO_SHA512
> +	select CRYPTO_HMAC
> +	select CRYPTO_SM3
> +	select CRYPTO_CMAC
> +	select CRYPTO_MICHAEL_MIC

[Severity: Low]
Does this select a non-existent config symbol? The CRYPTO_MICHAEL_MIC symbol
does not appear to exist in the kernel tree. Referencing a missing symbol in
a select statement can cause silent Kconfig failures.

> +	select CRYPTO_XCBC
> +	select CRYPTO_AES
> +	select CRYPTO_SM4_GENERIC

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260604165210.1141842-1-pavitrakumarm@vayavyalabs.com?part=4

      reply	other threads:[~2026-06-04 17:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 16:52 [PATCH v13 0/4] crypto: spacc - Add SPAcc Crypto Driver Pavitrakumar Managutte
2026-06-04 16:52 ` [PATCH v13 1/4] dt-bindings: crypto: Document support for SPAcc Pavitrakumar Managutte
2026-06-04 16:52 ` [PATCH v13 2/4] crypto: spacc - Add SPAcc ahash support Pavitrakumar Managutte
2026-06-04 17:12   ` sashiko-bot
2026-06-04 16:52 ` [PATCH v13 3/4] crypto: spacc - Add SPAcc AUTODETECT Support Pavitrakumar Managutte
2026-06-04 17:12   ` sashiko-bot
2026-06-04 16:52 ` [PATCH v13 4/4] crypto: spacc - Add SPAcc Kconfig and Makefile Pavitrakumar Managutte
2026-06-04 17:06   ` sashiko-bot [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=20260604170640.3CBC01F00898@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=pavitrakumarm@vayavyalabs.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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