From: "Mokhtar, Amr" <amr.mokhtar@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"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: [dpdk-dev] [PATCH v3 5/5] bbdev: documentation
Date: Tue, 19 Dec 2017 19:34:51 +0000 [thread overview]
Message-ID: <3D3765A8CDB52A4C8B410430AA19CB236EC63F05@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <1c842d19-62c1-2418-71f7-6ca5a4bb82d2@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Monday 11 December 2017 19:02
> To: Mokhtar, Amr <amr.mokhtar@intel.com>; dev@dpdk.org
> Cc: thomas@monjalon.net; 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: [dpdk-dev] [PATCH v3 5/5] bbdev: documentation
>
> On 12/7/2017 1:40 PM, Amr Mokhtar wrote:
> > - Wireless Baseband Device Library Programmer’s Guide
> > - test-bbdev User Guide
> > - BBDEV Sample Application User Guides
> > - Baseband Device Drivers Guides
> > - Doxygen API
> >
> > Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com>
> > ---
> > doc/api/doxy-api-index.md | 1 +
> > doc/api/doxy-api.conf | 1 +
> > doc/guides/bbdevs/index.rst | 40 +++
> > doc/guides/bbdevs/null.rst | 77 +++++
> > doc/guides/bbdevs/turbo_sw.rst | 175 ++++++++++
> > doc/guides/index.rst | 1 +
> > doc/guides/prog_guide/bbdev.rst | 613
> +++++++++++++++++++++++++++++++++
> > doc/guides/prog_guide/index.rst | 1 +
> > doc/guides/sample_app_ug/bbdev_app.rst | 160 +++++++++
> > doc/guides/sample_app_ug/index.rst | 1 +
> > doc/guides/tools/index.rst | 1 +
> > doc/guides/tools/testbbdev.rst | 600
> ++++++++++++++++++++++++++++++++
>
> You can also update release notes to announce new device abstraction layer.
Right. This was done already in patch 1/5 to introduce the new device abstraction library
along with its source files in lib/librte_bbdev/
Thanks for your feedback,
Amr
next prev parent reply other threads:[~2017-12-19 19:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 21:40 [dpdk-dev] [PATCH v3 1/5] bbdev: librte_bbdev library Amr Mokhtar
2017-12-07 21:40 ` [dpdk-dev] [PATCH v3 2/5] bbdev: PMD drivers (null/turbo_sw) Amr Mokhtar
2017-12-11 19:00 ` Ferruh Yigit
2017-12-19 19:09 ` Mokhtar, Amr
2017-12-07 21:40 ` [dpdk-dev] [PATCH v3 3/5] bbdev: test applications Amr Mokhtar
2017-12-11 19:01 ` Ferruh Yigit
2017-12-23 0:09 ` Mokhtar, Amr
2017-12-07 21:40 ` [dpdk-dev] [PATCH v3 4/5] bbdev: sample app Amr Mokhtar
2017-12-07 21:40 ` [dpdk-dev] [PATCH v3 5/5] bbdev: documentation Amr Mokhtar
2017-12-11 19:01 ` Ferruh Yigit
2017-12-19 19:34 ` Mokhtar, Amr [this message]
2017-12-18 14:26 ` Kovacevic, Marko
2017-12-23 0:11 ` Mokhtar, Amr
2017-12-07 21:40 ` [dpdk-dev] [PATCH v3 0/5] Wireless Baseband Device (bbdev) Amr Mokhtar
2017-12-09 2:44 ` [dpdk-dev] [PATCH v3 1/5] bbdev: librte_bbdev library Ferruh Yigit
2017-12-19 19:03 ` Mokhtar, Amr
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=3D3765A8CDB52A4C8B410430AA19CB236EC63F05@IRSMSX104.ger.corp.intel.com \
--to=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 \
--cc=thomas@monjalon.net \
/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).