From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: harry.van.haaren@intel.com, john.mcnamara@intel.com,
marko.kovacevic@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: add eventdev pipeline sample app to release notes
Date: Tue, 16 Jan 2018 20:41:51 +0530 [thread overview]
Message-ID: <20180116151150.GC2651@jerin> (raw)
In-Reply-To: <20180116150526.32096-1-pbhagavatula@caviumnetworks.com>
-----Original Message-----
> Date: Tue, 16 Jan 2018 20:35:26 +0530
> From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> To: jerin.jacob@caviumnetworks.com, harry.van.haaren@intel.com,
> john.mcnamara@intel.com, marko.kovacevic@intel.com
> Cc: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> Subject: [dpdk-dev] [PATCH] doc: add eventdev pipeline sample app to
> release notes
> X-Mailer: git-send-email 2.14.1
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> ---
>
> This patch depends on http://dpdk.org/dev/patchwork/patch/33429 patchset.
>
> doc/guides/rel_notes/release_18_02.rst | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/doc/guides/rel_notes/release_18_02.rst b/doc/guides/rel_notes/release_18_02.rst
> index b2dc39cfe..11b8d889e 100644
> --- a/doc/guides/rel_notes/release_18_02.rst
> +++ b/doc/guides/rel_notes/release_18_02.rst
> @@ -53,6 +53,12 @@ New Features
>
> With this change, application can use OPDL PMD by eventdev api.
>
> +* **Update Eventdev Sample application to support event devices based on caps**
IMO, it is better to change the caps to capabilities
> + Update Eventdev pipeline sample application to support various types of
> + pipelines based on the capabilities of the attached event and ethernet
> + devices. And renamed the application from ``eventdev_pipeline_sw_pmd`` to
How about,
and renamed the application from SW PMD specific ``eventdev_pipeline_sw_pmd``
to PMD agnostic ``eventdev_pipeline``.
> + ``eventdev_pipeline``.
> +
> API Changes
> -----------
>
> --
> 2.14.1
>
next prev parent reply other threads:[~2018-01-16 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 15:05 Pavan Nikhilesh
2018-01-16 15:11 ` Jerin Jacob [this message]
2018-01-16 18:06 ` [dpdk-dev] [PATCH v2] " Pavan Nikhilesh
2018-01-17 16:56 ` Mcnamara, John
2018-01-17 17:22 ` Jerin Jacob
2018-01-17 16:58 ` Mcnamara, John
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=20180116151150.GC2651@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=pbhagavatula@caviumnetworks.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).