DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: kai.ji@intel.com, akhil.goyal@marvell.com, dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] crypto/qat: fix build
Date: Thu, 12 Jan 2023 21:39:59 +0100	[thread overview]
Message-ID: <111861575.nniJfEyVGO@thomas> (raw)
In-Reply-To: <20230112193045.2907753-1-pablo.de.lara.guarch@intel.com>

12/01/2023 20:30, Pablo de Lara:
> Instead of undefining AES_BLOCK_SIZE, define NO_COMPAT_IMB_API_053,
> which prevents legacy macros like AES_BLOCK_SIZE from being defined
> from IPSec MB library.

Given we are discarding my first workaround,
your first sentence doesn't really make sense.
Please give more context, explain the conflict with OpenSSL,
and copy the error message.

Thanks

> Fixes: 3227bc7138f5 ("crypto/qat: use intel-ipsec-mb for partial hash and AES")
> Cc: stable@dpdk.org
> Cc: kai.ji@intel.com
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>




  reply	other threads:[~2023-01-12 20:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 19:30 Pablo de Lara
2023-01-12 20:39 ` Thomas Monjalon [this message]
2023-01-17  8:22   ` [EXT] " Akhil Goyal
2023-01-18  9:51     ` De Lara Guarch, Pablo
2023-01-18 11:05 ` [PATCH v2] " Pablo de Lara
2023-01-18 14:17   ` Ji, Kai
2023-01-19  9:35     ` Akhil Goyal
  -- strict thread matches above, loose matches on Subject: below --
2022-12-30 21:07 [PATCH] " Thomas Monjalon
2022-12-30 21:38 ` Tyler Retzlaff
2023-01-04 11:56 ` [EXT] " Akhil Goyal
2023-01-11  9:03   ` Thomas Monjalon
2023-01-11 23:20     ` Thomas Monjalon
2023-01-12 10:32       ` Ji, Kai
2023-01-12 10:40         ` Thomas Monjalon
2023-01-12 13:22           ` De Lara Guarch, Pablo
2023-01-12 15:00             ` Thomas Monjalon
2023-01-12 16:16               ` De Lara Guarch, Pablo
2023-01-12 16:28                 ` Thomas Monjalon
2023-01-12 16:34             ` Tyler Retzlaff

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=111861575.nniJfEyVGO@thomas \
    --to=thomas@monjalon.net \
    --cc=akhil.goyal@marvell.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=pablo.de.lara.guarch@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).