From: Thomas Monjalon <thomas@monjalon.net>
To: Ciara Power <ciara.power@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"nishikanta.nayak@intel.com" <nishikanta.nayak@intel.com>,
Kai Ji <kai.ji@intel.com>, Ali Alnubani <alialnu@nvidia.com>
Subject: Re: [PATCH] common/qat: fix undefined macro
Date: Tue, 05 Mar 2024 14:17:14 +0100 [thread overview]
Message-ID: <21110049.0c2gjJ1VT2@thomas> (raw)
In-Reply-To: <DM4PR12MB51673D227254CDD805778D60DA222@DM4PR12MB5167.namprd12.prod.outlook.com>
05/03/2024 13:15, Ali Alnubani:
> > -----Original Message-----
> > From: Ciara Power <ciara.power@intel.com>
> > Sent: Tuesday, March 5, 2024 1:56 PM
> > To: dev@dpdk.org
> > Cc: gakhil@marvell.com; Ciara Power <ciara.power@intel.com>;
> > nishikanta.nayak@intel.com; Kai Ji <kai.ji@intel.com>
> > Subject: [PATCH] common/qat: fix undefined macro
> >
> > When using RTE_ENABLE_ASSERT and debug mode, an undefined
> > macro error appeared for ICP_QAT_FW_SYM_COMM_ADDR_SGL.
> > This was not being defined, but is now added to the header file.
> >
> > Bugzilla ID: 1395
> > Fixes: e9271821e489 ("common/qat: support GEN LCE device")
> >
> > Signed-off-by: Ciara Power <ciara.power@intel.com>
> >
> > ---
>
> Can confirm it resolves the build failure, thanks!
>
> Tested-by: Ali Alnubani <alialnu@nvidia.com>
Reported-by: Ali Alnubani <alialnu@nvidia.com>
Applied, thanks.
prev parent reply other threads:[~2024-03-05 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 11:55 [PATCH] common/qat: fix undefined macro Ciara Power
2024-03-05 12:08 ` Nayak, Nishikanta
2024-03-05 12:15 ` Ali Alnubani
2024-03-05 13:17 ` Thomas Monjalon [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=21110049.0c2gjJ1VT2@thomas \
--to=thomas@monjalon.net \
--cc=alialnu@nvidia.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
--cc=nishikanta.nayak@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.