From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Rosen, Rami" <rami.rosen@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: fix a typo in ip pipeline app guide
Date: Tue, 31 Oct 2017 09:38:46 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BADBEF0@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1509177471-19628-1-git-send-email-rami.rosen@intel.com>
> -----Original Message-----
> From: Rosen, Rami
> Sent: Saturday, October 28, 2017 8:58 AM
> To: dev@dpdk.org
> Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Rosen, Rami
> <rami.rosen@intel.com>
> Subject: [PATCH] doc: fix a typo in ip pipeline app guide
>
> This patch fixes a trivial typo in ip pipeline app guide.
>
> Signed-off-by: Rami Rosen <rami.rosen@intel.com>
> ---
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
next prev parent reply other threads:[~2017-10-31 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 7:57 Rami Rosen
2017-10-31 9:38 ` Dumitrescu, Cristian [this message]
2017-11-02 17:02 ` Mcnamara, John
2017-11-13 5:31 ` 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=3EB4FA525960D640B5BDFFD6A3D891267BADBEF0@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=rami.rosen@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).