From: Akhil Goyal <gakhil@marvell.com>
To: David Marchand <david.marchand@redhat.com>, Kai Ji <kai.ji@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
Ciara Power <ciara.power@intel.com>,
Fan Zhang <fanzhang.oss@gmail.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: RE: [EXT] Re: [PATCH] crypto/qat: fix build for generic x86 with GCC 12
Date: Tue, 17 Jan 2023 08:20:48 +0000 [thread overview]
Message-ID: <CO6PR18MB44844293246602DD308DAA5CD8C69@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8xMxWj-RQk3OyvycGa+ydz+xTHeCTGSaFgGstTDeZu3bg@mail.gmail.com>
> On Tue, Jan 10, 2023 at 12:27 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > On Mon, Jan 09, 2023 at 11:34:36AM +0100, David Marchand wrote:
> > > Similar to commit 04361fe2aca8 ("crypto/qat: fix build with GCC 12").
> > > The issue appears when building with the "generic" target we have in
> > > devtools/test-meson-builds.sh.
> > >
> > > Fixes: 3227bc7138f5 ("crypto/qat: use intel-ipsec-mb for partial hash and
> AES")
> > > Cc: stable@dpdk.org
> > >
> > > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > > ---
> > > drivers/crypto/qat/qat_sym_session.c | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > Confirm that this fixes the build issue.
> >
> > Tested-by: Bruce Richardson <bruce.richardson@intel.com>
> >
>
> No objection from maintainer, Akhil, can you take this to next-crypto?
Sure, will merge today/tomorrow.
next prev parent reply other threads:[~2023-01-17 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 10:34 David Marchand
2023-01-10 11:26 ` Bruce Richardson
2023-01-17 8:10 ` David Marchand
2023-01-17 8:20 ` Akhil Goyal [this message]
2023-01-17 9:02 ` [EXT] " Bruce Richardson
2023-01-19 9:37 ` Akhil Goyal
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=CO6PR18MB44844293246602DD308DAA5CD8C69@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=kai.ji@intel.com \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).