From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: marko.kovacevic@intel.com, john.mcnamara@intel.com,
liang.j.ma@intel.com, dev@dpdk.org
Subject: Re: [PATCH] doc: fix OPDL release notes
Date: Thu, 18 Jan 2018 11:31:02 +0530 [thread overview]
Message-ID: <20180118060101.GA18465@jerin> (raw)
In-Reply-To: <20180117172509.30088-1-pbhagavatula@caviumnetworks.com>
-----Original Message-----
> Date: Wed, 17 Jan 2018 22:55:09 +0530
> From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> To: jerin.jacob@caviumnetworks.com, marko.kovacevic@intel.com,
> john.mcnamara@intel.com, liang.j.ma@intel.com
> Cc: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> Subject: [dpdk-dev] [PATCH] doc: fix OPDL release notes
> X-Mailer: git-send-email 2.14.1
>
> Fixes: a507e3320e34 ("doc: update 18.02 release notes and maintainers")
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Thanks, Squashed this change in next-eventdev tree.
> ---
> doc/guides/rel_notes/release_18_02.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/doc/guides/rel_notes/release_18_02.rst b/doc/guides/rel_notes/release_18_02.rst
> index b2dc39cfe..cdfdb202e 100644
> --- a/doc/guides/rel_notes/release_18_02.rst
> +++ b/doc/guides/rel_notes/release_18_02.rst
> @@ -43,6 +43,7 @@ New Features
>
>
> * **Added New eventdev OPDL PMD**
> +
> The OPDL (Ordered Packet Distribution Library) eventdev is a specific
> implementation of the eventdev API. It is particularly suited to packet
> processing workloads that have high throughput and low latency requirements.
> --
> 2.14.1
>
prev parent reply other threads:[~2018-01-18 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:25 [PATCH] doc: fix OPDL release notes Pavan Nikhilesh
2018-01-18 6:01 ` Jerin Jacob [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=20180118060101.GA18465@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=liang.j.ma@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 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.