From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add eventdev pipeline sample app to release notes
Date: Wed, 17 Jan 2018 22:52:59 +0530 [thread overview]
Message-ID: <20180117172258.GB24121@jerin> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23EE755E3@IRSMSX103.ger.corp.intel.com>
-----Original Message-----
> Date: Wed, 17 Jan 2018 16:56:47 +0000
> From: "Mcnamara, John" <john.mcnamara@intel.com>
> To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
> "jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
> "Kovacevic, Marko" <marko.kovacevic@intel.com>
> CC: "dev@dpdk.org" <dev@dpdk.org>
> Subject: RE: [dpdk-dev] [PATCH v2] doc: add eventdev pipeline sample app to
> release notes
>
>
>
> > -----Original Message-----
> > From: Pavan Nikhilesh [mailto:pbhagavatula@caviumnetworks.com]
> > Sent: Tuesday, January 16, 2018 6:06 PM
> > To: jerin.jacob@caviumnetworks.com; Kovacevic, Marko
> > <marko.kovacevic@intel.com>; Mcnamara, John <john.mcnamara@intel.com>
> > Cc: dev@dpdk.org; Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> > Subject: [dpdk-dev] [PATCH v2] doc: add eventdev pipeline sample app to
> > release notes
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied to dpdk-next-eventdev/master. Thanks.
>
>
next prev parent reply other threads:[~2018-01-17 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 15:05 [dpdk-dev] [PATCH] " Pavan Nikhilesh
2018-01-16 15:11 ` Jerin Jacob
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 [this message]
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=20180117172258.GB24121@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--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).