From: "Cabiddu, Giovanni" <giovanni.cabiddu@intel.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Karthikeyan Gopal <karthikeyan.gopal@intel.com>,
Laurent M Coquerel <laurent.m.coquerel@intel.com>,
Suman Kumar Chakraborty <suman.kumar.chakraborty@intel.com>,
Arnd Bergmann <arnd@arndb.de>,
"George Abraham P" <george.abraham.p@intel.com>,
<qat-linux@intel.com>, <linux-crypto@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: qat - add missing header inclusion
Date: Wed, 21 May 2025 05:56:15 +0100 [thread overview]
Message-ID: <aC1c7+PQZN++5mgf@gcabiddu-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <20250520161148.3562622-1-arnd@kernel.org>
On Tue, May 20, 2025 at 06:11:36PM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> Without this header, building the new driver fails with:
>
> In file included from drivers/crypto/intel/qat/qat_common/adf_gen6_shared.c:7:
> drivers/crypto/intel/qat/qat_common/adf_gen4_pfvf.h: In function 'adf_gen4_init_pf_pfvf_ops':
> drivers/crypto/intel/qat/qat_common/adf_gen4_pfvf.h:13:34: error: 'adf_pfvf_comms_disabled' undeclared (first use in this function)
> 13 | pfvf_ops->enable_comms = adf_pfvf_comms_disabled;
> | ^~~~~~~~~~~~~~~~~~~~~~~
>
> Fixes: 17fd7514ae68 ("crypto: qat - add qat_6xxx driver")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Thanks Arnd. This occurs with CONFIG_PCI_IOV not set. Can this be added
to the commit message?
> ---
> drivers/crypto/intel/qat/qat_common/adf_gen2_pfvf.h | 1 +
> drivers/crypto/intel/qat/qat_common/adf_gen4_pfvf.h | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/drivers/crypto/intel/qat/qat_common/adf_gen2_pfvf.h b/drivers/crypto/intel/qat/qat_common/adf_gen2_pfvf.h
> index a716545a764c..9efee0053f3a 100644
> --- a/drivers/crypto/intel/qat/qat_common/adf_gen2_pfvf.h
> +++ b/drivers/crypto/intel/qat/qat_common/adf_gen2_pfvf.h
> @@ -4,6 +4,7 @@
> #define ADF_GEN2_PFVF_H
>
> #include <linux/types.h>
> +#include "adf_common_drv.h"
> #include "adf_accel_devices.h"
NIT. Can this be in alphabetical order?
>
> #define ADF_GEN2_ERRSOU3 (0x3A000 + 0x0C)
> diff --git a/drivers/crypto/intel/qat/qat_common/adf_gen4_pfvf.h b/drivers/crypto/intel/qat/qat_common/adf_gen4_pfvf.h
> index 17d1b774d4a8..2c8708117f70 100644
> --- a/drivers/crypto/intel/qat/qat_common/adf_gen4_pfvf.h
> +++ b/drivers/crypto/intel/qat/qat_common/adf_gen4_pfvf.h
> @@ -4,6 +4,7 @@
> #define ADF_GEN4_PFVF_H
>
> #include "adf_accel_devices.h"
> +#include "adf_common_drv.h"
>
> #ifdef CONFIG_PCI_IOV
> void adf_gen4_init_pf_pfvf_ops(struct adf_pfvf_ops *pfvf_ops);
Thanks,
--
Giovanni
next prev parent reply other threads:[~2025-05-21 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 16:11 [PATCH] crypto: qat - add missing header inclusion Arnd Bergmann
2025-05-21 4:56 ` Cabiddu, Giovanni [this message]
2025-05-22 10:21 ` [PATCH v2] " Cabiddu, Giovanni
2025-05-23 11:27 ` 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=aC1c7+PQZN++5mgf@gcabiddu-mobl.ger.corp.intel.com \
--to=giovanni.cabiddu@intel.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=davem@davemloft.net \
--cc=george.abraham.p@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=karthikeyan.gopal@intel.com \
--cc=laurent.m.coquerel@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=suman.kumar.chakraborty@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