From: Julian Braha <julianbraha@gmail.com>
To: Pavitrakumar Managutte <pavitrakumarm@vayavyalabs.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, herbert@gondor.apana.org.au,
robh@kernel.org
Cc: krzk@kernel.org, conor+dt@kernel.org, Ruud.Derwig@synopsys.com,
rbannerm@synopsys.com, manjunath.hadli@vayavyalabs.com,
adityak@vayavyalabs.com, navami.telsang@vayavyalabs.com,
bhoomikak@vayavyalabs.com
Subject: Re: [PATCH v16 4/4] crypto: spacc - Add SPAcc Kconfig and Makefile
Date: Fri, 10 Jul 2026 13:27:25 +0100 [thread overview]
Message-ID: <5ca48a5f-086d-4372-ab3c-1535dcdbe5fc@gmail.com> (raw)
In-Reply-To: <20260707125311.2398031-5-pavitrakumarm@vayavyalabs.com>
Hi Pavitrakumar,
On 7/7/26 13:53, Pavitrakumar Managutte wrote:
> +config CRYPTO_DEV_SPACC_CONFIG_DEBUG
> + bool "Enable SPAcc debug logs"
> + default n
> + help
> + Say y to enable additional debug prints and diagnostics in the
> + SPAcc driver. Disable this for production builds.
This help text still has the indentation formatting issue that I pointed
out on v15:
https://lore.kernel.org/all/deb73385-a7a9-4ea9-8338-b7da999a5e9c@gmail.com/
- Julian Braha
prev parent reply other threads:[~2026-07-10 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 12:53 [PATCH v16 0/4] crypto: spacc - Add SPAcc Crypto Driver Pavitrakumar Managutte
2026-07-07 12:53 ` [PATCH v16 1/4] dt-bindings: crypto: Document support for SPAcc Pavitrakumar Managutte
2026-07-07 12:53 ` [PATCH v16 2/4] crypto: spacc - Add SPAcc ahash support Pavitrakumar Managutte
2026-07-07 12:53 ` [PATCH v16 3/4] crypto: spacc - Add SPAcc AUTODETECT Support Pavitrakumar Managutte
2026-07-07 12:53 ` [PATCH v16 4/4] crypto: spacc - Add SPAcc Kconfig and Makefile Pavitrakumar Managutte
2026-07-10 12:27 ` Julian Braha [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=5ca48a5f-086d-4372-ab3c-1535dcdbe5fc@gmail.com \
--to=julianbraha@gmail.com \
--cc=Ruud.Derwig@synopsys.com \
--cc=adityak@vayavyalabs.com \
--cc=bhoomikak@vayavyalabs.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzk@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manjunath.hadli@vayavyalabs.com \
--cc=navami.telsang@vayavyalabs.com \
--cc=pavitrakumarm@vayavyalabs.com \
--cc=rbannerm@synopsys.com \
--cc=robh@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