DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	Dharmik Thakkar <Dharmik.Thakkar@arm.com>
Cc: Ruifeng Wang <Ruifeng.Wang@arm.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Akhil.goyal@nxp.com" <akhil.goyal@nxp.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] doc: update build guide for armv8 crypto PMD
Date: Tue, 27 Oct 2020 09:45:28 +0100	[thread overview]
Message-ID: <2366603.Tc9MNis146@thomas> (raw)
In-Reply-To: <96A756D0-D72E-4DE4-95D3-AAEA62395609@arm.com>

27/10/2020 05:18, Dharmik Thakkar:
> 
> > On Oct 22, 2020, at 4:25 PM, Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com> wrote:
> > 
> > + Dharmik
> > 
> > From: Thomas Monjalon <thomas@monjalon.net>
> >> 14/10/2020 11:24, Ruifeng Wang:
> >>> +* Build DPDK with meson option ``-
> >> Darmv8_crypto_dir=<path_to_AArch64cryptolib>``:
> >>> +
> >>> +meson -Darmv8_crypto_dir=<path_to_AArch64cryptolib> build
> >> 
> >> Please, could you add pkg-config support to this lib?
> >> I would like to remove with option from DPDK, and use the standard variable
> >> PKG_CONFIG_PATH instead.
> > If I remember correct, Dharmik had a patch for this.
> 
> I have created a pull request to add pkg-config support to the AArch64crypto library.
> Once it is merged, I will submit a patch to remove the meson option.

Wonderful, thank you




      reply	other threads:[~2020-10-27  8:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14  9:24 Ruifeng Wang
2020-10-14 14:10 ` Honnappa Nagarahalli
2020-10-14 14:19   ` Ruifeng Wang
2020-10-14 14:24     ` Honnappa Nagarahalli
2020-10-22 21:10 ` Thomas Monjalon
2020-10-22 21:17 ` Thomas Monjalon
2020-10-22 21:25   ` Honnappa Nagarahalli
2020-10-27  4:18     ` Dharmik Thakkar
2020-10-27  8:45       ` 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=2366603.Tc9MNis146@thomas \
    --to=thomas@monjalon.net \
    --cc=Dharmik.Thakkar@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.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;
as well as URLs for NNTP newsgroup(s).