On Tue, Jan 17, 2023 at 08:20:48AM +0000, Akhil Goyal wrote:
> > On Tue, Jan 10, 2023 at 12:27 PM Bruce Richardson
> > <bruce.richard...@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: sta...@dpdk.org
> > > >
> > > > Signed-off-by: David Marchand <david.march...@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.richard...@intel.com>
> > >
> >
> > No objection from maintainer, Akhil, can you take this to next-crypto?
> Sure, will merge today/tomorrow.
Once merged into crypto can it be quickly pulled into the main tree, as the
build error is also seen there? I think build issues should generally be
fixed directly on main, as they affect those not working in the particular
subtree area.
