DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
	Nicolas Chautru <nicolas.chautru@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"ciara.power@intel.com" <ciara.power@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] baseband/turbo_sw: update meson for more dynamic compilation
Date: Tue, 6 Oct 2020 21:18:58 +0000	[thread overview]
Message-ID: <VI1PR04MB3168FAC017E33F8EEE88BDC4E60D0@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200904093121.GC1627@bricha3-MOBL.ger.corp.intel.com>

> 
> On Thu, Sep 03, 2020 at 06:05:35PM -0700, Nicolas Chautru wrote:
> > The meson for the turbo_sw PMD is updated to prevent the
> > requirement for any device specific toplevel flags to be
> > passed down (unlike what used to be the case with make).
> > The linking to the optional libraries is purely auto
> > detected at build time and flags are then set appropriately.
> >
> > Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> > ---
> >  drivers/baseband/turbo_sw/meson.build | 43 ++++++++++++++++++------------
> -----
> >  1 file changed, 22 insertions(+), 21 deletions(-)
> >
> 
> From a meson viewpoint this all looks good, and glad to see the driver
> taking advantage of the dynamic probing.
> 
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> 
Applied to dpdk-next-crypto
Thanks.

      reply	other threads:[~2020-10-06 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04  1:05 Nicolas Chautru
2020-09-04  1:05 ` Nicolas Chautru
2020-09-04  9:31   ` Bruce Richardson
2020-10-06 21:18     ` Akhil Goyal [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=VI1PR04MB3168FAC017E33F8EEE88BDC4E60D0@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=nicolas.chautru@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 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).