From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrzej Ostruszka <aostruszka@marvell.com>,
dev@dpdk.org, Keith Wiles <keith.wiles@intel.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] doc: minor fixes in tap guide
Date: Thu, 21 Nov 2019 16:32:11 +0000 [thread overview]
Message-ID: <9b867e35-3f44-e4ab-d215-2c5707f639a4@intel.com> (raw)
In-Reply-To: <20191121132701.31856-1-aostruszka@marvell.com>
On 11/21/2019 1:27 PM, Andrzej Ostruszka wrote:
> Corrected one typo and ip address.
>
> Signed-off-by: Andrzej Ostruszka <aostruszka@marvell.com>
>
> Fixes: de96fe68ae95 ("net/tap: add basic flow API patterns and actions")
> Cc: stable@dpdk.org
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-11-21 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 13:27 [dpdk-dev] " Andrzej Ostruszka
2019-11-21 16:32 ` Ferruh Yigit [this message]
2019-11-21 16:59 ` Stephen Hemminger
2019-11-22 9:19 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2019-11-22 12:25 ` Ferruh Yigit
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=9b867e35-3f44-e4ab-d215-2c5707f639a4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=aostruszka@marvell.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=keith.wiles@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=stable@dpdk.org \
/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).