From: Thomas Monjalon <thomas@monjalon.net>
To: "Mokhtar, Amr" <amr.mokhtar@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Power, Niall" <niall.power@intel.com>,
"Macnamara, Chris" <chris.macnamara@intel.com>
Subject: Re: [PATCH v5 0/5] Introducing Wirless Base Band Device (bbdev) abstraction library
Date: Wed, 31 Jan 2018 21:41:25 +0100 [thread overview]
Message-ID: <10330486.sAcIo0Kpun@xps> (raw)
In-Reply-To: <3D3765A8CDB52A4C8B410430AA19CB236EC82832@IRSMSX104.ger.corp.intel.com>
31/01/2018 21:29, Mokhtar, Amr:
> From: Thomas Monjalon
> > 11/01/2018 20:23, Amr Mokhtar:
> > > Hello,
> > > Latest update for Wireless Device abstraction library.
> >
> > Applied with few changes:
> > - fixed title formats
> > - moved bbdev between ethdev and cryptodev in lists
> > - added in test-build.sh
> > - fixed compilation as shared library (must be better fixed in RC2)
> > undefined reference to `bbdev_logtype', added to .map
>
> Can you explain more what shared library compilation problem
> were experienced? Is it the missing 'bbdev_logtype' ?
Yes
Please avoid exporting this variable.
prev parent reply other threads:[~2018-01-31 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 19:23 [PATCH v5 1/5] bbdev: introducing wireless base band device abstraction lib Amr Mokhtar
2018-01-11 19:23 ` [PATCH v5 2/5] bbdev: null device driver Amr Mokhtar
2018-01-11 19:23 ` [PATCH v5 3/5] bbdev: software turbo driver Amr Mokhtar
2018-01-19 0:23 ` Thomas Monjalon
2018-01-31 18:20 ` Mokhtar, Amr
2018-01-11 19:23 ` [PATCH v5 4/5] bbdev: test applications Amr Mokhtar
2018-01-11 19:23 ` [PATCH v5 5/5] bbdev: sample app Amr Mokhtar
2018-01-11 19:23 ` [PATCH v5 0/5] Introducing Wirless Base Band Device (bbdev) abstraction library Amr Mokhtar
2018-01-19 0:45 ` Thomas Monjalon
2018-01-31 20:29 ` Mokhtar, Amr
2018-01-31 20:41 ` 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=10330486.sAcIo0Kpun@xps \
--to=thomas@monjalon.net \
--cc=amr.mokhtar@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=chris.macnamara@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=niall.power@intel.com \
--cc=pablo.de.lara.guarch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.