From: Olivier Matz <olivier.matz@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org, Chas Williams <3chas3@gmail.com>
Subject: Re: [dpdk-stable] [PATCH] mbuf: update Tx VLAN and QinQ mbuf flags documentation
Date: Mon, 8 Apr 2019 09:16:49 +0200 [thread overview]
Message-ID: <20190408071649.2hywjjy557yzor4y@platinum> (raw)
In-Reply-To: <20190402170947.8134-1-ferruh.yigit@intel.com>
On Tue, Apr 02, 2019 at 06:09:46PM +0100, Ferruh Yigit wrote:
> Currently PKT_TX_VLAN and PKT_TX_QINQ mbuf flags are documented as
> they are to say packet contains VLAN or QINQ information.
>
> Updating the definition as they are requests from application to
> driver to insert VLAN or double VLAN tags into packet.
>
> Fixes: dc6c911c9993 ("mbuf: use reserved space for double vlan")
> Fixes: af75078fece3 ("first public release")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> Cc: Chas Williams <3chas3@gmail.com>
> ---
> lib/librte_mbuf/rte_mbuf.h | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
Acked-by: Olivier Matz <olivier.matz@6wind.com>
Thanks
next prev parent reply other threads:[~2019-04-08 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 17:09 Ferruh Yigit
2019-04-08 7:16 ` Olivier Matz [this message]
2019-04-19 20:56 ` [dpdk-stable] [dpdk-dev] " 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=20190408071649.2hywjjy557yzor4y@platinum \
--to=olivier.matz@6wind.com \
--cc=3chas3@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).