DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Amr Mokhtar <amr.mokhtar@intel.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, anatoly.burakov@intel.com,
	pablo.de.lara.guarch@intel.com, niall.power@intel.com,
	chris.macnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v5 0/5] Introducing Wirless Base Band Device (bbdev) abstraction library
Date: Fri, 19 Jan 2018 01:45:28 +0100	[thread overview]
Message-ID: <1596883.yZ5vjCyqb0@xps> (raw)
In-Reply-To: <1515698603-20416-6-git-send-email-amr.mokhtar@intel.com>

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

Thanks for the good work, and welcome in DPDK!

  reply	other threads:[~2018-01-19  0:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 19:23 [dpdk-dev] [PATCH v5 1/5] bbdev: introducing wireless base band device abstraction lib Amr Mokhtar
2018-01-11 19:23 ` [dpdk-dev] [PATCH v5 2/5] bbdev: null device driver Amr Mokhtar
2018-01-11 19:23 ` [dpdk-dev] [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 ` [dpdk-dev] [PATCH v5 4/5] bbdev: test applications Amr Mokhtar
2018-01-11 19:23 ` [dpdk-dev] [PATCH v5 5/5] bbdev: sample app Amr Mokhtar
2018-01-11 19:23 ` [dpdk-dev] [PATCH v5 0/5] Introducing Wirless Base Band Device (bbdev) abstraction library Amr Mokhtar
2018-01-19  0:45   ` Thomas Monjalon [this message]
2018-01-31 20:29     ` Mokhtar, Amr
2018-01-31 20:41       ` Thomas Monjalon

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=1596883.yZ5vjCyqb0@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 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).