From: Horia Geanta <horia.geanta@nxp.com>
To: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
Pankaj Gupta <pankaj.gupta@nxp.com>,
Gaurav Jain <gaurav.jain@nxp.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] caamalg: Make use of dev_*() instead of pr_*()
Date: Wed, 23 Apr 2025 09:22:02 +0000 [thread overview]
Message-ID: <dbf1577c-220d-4eff-bc1d-649d0d70678c@nxp.com> (raw)
In-Reply-To: <2025042122-infrared-bumblebee-b2d3dc@boujee-and-buff>
On 4/23/2025 10:29 AM, Ben Collins wrote:
> It's nice when messages line up with the device, and easy to implement
> since it's already available in the functions.
>
> Signed-off-by: Ben Collins <bcollins@kernel.org>
> Cc: "Horia Geantă" <horia.geanta@nxp.com>
> Cc: Pankaj Gupta <pankaj.gupta@nxp.com>
> Cc: Gaurav Jain <gaurav.jain@nxp.com>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: linux-crypto@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> ---
> drivers/crypto/caam/caamalg.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/crypto/caam/caamalg.c b/drivers/crypto/caam/caamalg.c
> index 2cfb1b8d8c7cf..d964a62ef9668 100644
> --- a/drivers/crypto/caam/caamalg.c
> +++ b/drivers/crypto/caam/caamalg.c
> @@ -3633,7 +3633,7 @@ static int caam_cra_init(struct crypto_skcipher *tfm)
> fallback = crypto_alloc_skcipher(tfm_name, 0,
> CRYPTO_ALG_NEED_FALLBACK);
> if (IS_ERR(fallback)) {
> - pr_err("Failed to allocate %s fallback: %ld\n",
> + dev_err(ctx->jrdev, "Failed to allocate %s fallback: %ld\n",
ctx->jrdev is not initialized at this point;
it's done later in caam_init_common().
Actually, we've fixed the same issue some time ago in commit
ab95bd2aa904 ("crypto: caam - fix printing on xts fallback allocation error path")
Thanks,
Horia
prev parent reply other threads:[~2025-04-23 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 2:41 Ben Collins
2025-04-23 9:22 ` Horia Geanta [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=dbf1577c-220d-4eff-bc1d-649d0d70678c@nxp.com \
--to=horia.geanta@nxp.com \
--cc=davem@davemloft.net \
--cc=gaurav.jain@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.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 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®