From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
To: Haowen Bai <baihaowen@meizu.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
qat-linux@intel.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: qat - Fix unsigned function returning negative constant
Date: Mon, 25 Apr 2022 15:34:53 +0100 [thread overview]
Message-ID: <YmaxfKXqYNOgGXYI@silpixa00400314> (raw)
In-Reply-To: <1650790231-16894-1-git-send-email-baihaowen@meizu.com>
On Sun, Apr 24, 2022 at 04:50:31PM +0800, Haowen Bai wrote:
> The function qat_uclo_check_image_compat has an unsigned return type, but
Nit, function names should have parenthesis: qat_uclo_check_image_compat()
> returns a negative constant to indicate an error condition. So we change
> unsigned to int.
>
> Signed-off-by: Haowen Bai <baihaowen@meizu.com>
Fixes: b4b7e67c917f ("crypto: qat - Intel(R) QAT ucode part of fw loader")
Acked-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
> ---
> drivers/crypto/qat/qat_common/qat_uclo.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/qat/qat_common/qat_uclo.c b/drivers/crypto/qat/qat_common/qat_uclo.c
> index 6356402a2c9e..4b6f37d6e85b 100644
> --- a/drivers/crypto/qat/qat_common/qat_uclo.c
> +++ b/drivers/crypto/qat/qat_common/qat_uclo.c
> @@ -519,7 +519,7 @@ qat_uclo_map_chunk(char *buf, struct icp_qat_uof_filehdr *file_hdr,
> return NULL;
> }
>
> -static unsigned int
> +static int
> qat_uclo_check_image_compat(struct icp_qat_uof_encap_obj *encap_uof_obj,
> struct icp_qat_uof_image *image)
> {
> --
> 2.7.4
>
next prev parent reply other threads:[~2022-04-25 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 8:50 [PATCH] crypto: qat - Fix unsigned function returning negative constant Haowen Bai
2022-04-25 14:34 ` Giovanni Cabiddu [this message]
2022-04-29 5:50 ` Herbert Xu
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=YmaxfKXqYNOgGXYI@silpixa00400314 \
--to=giovanni.cabiddu@intel.com \
--cc=baihaowen@meizu.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.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