From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Olivier Matz <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"arybchenko@solarflare.com" <arybchenko@solarflare.com>,
"Jacob, Jerin" <Jerin.JacobKollanukkaran@cavium.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] mbuf: fix missing Tx offload flag name and list update
Date: Tue, 16 Oct 2018 14:55:10 +0100 [thread overview]
Message-ID: <139362d2-a40a-f23d-99a7-142e02265ef8@intel.com> (raw)
In-Reply-To: <0e734fee-5a49-3213-b34d-5b9a06dae30f@intel.com>
On 10/16/2018 2:42 PM, Ferruh Yigit wrote:
> On 10/16/2018 1:45 PM, Jerin Jacob wrote:
>> Fix missing PKT_TX* ol_flag name and list updatation.
>>
>> Fixes: 6d18505efaa6 ("vhost: support UDP Fragmentation Offload")
>> Fixes: 829a1c2c41dc ("mbuf: extend flow director field")
>> Fixes: 63c0d74daaa9 ("mbuf: add Tx side tunneling type")
>>
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
>
> For series,
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> (since now updated for both Rx & Tx, patch title needs to be updated, I will do
> it while merging)
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-10-16 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 19:34 [dpdk-dev] [PATCH " Jerin Jacob
2018-10-11 19:34 ` [dpdk-dev] [PATCH 2/2] mbuf: fix missing Tx outer UDP checksum flag name Jerin Jacob
2018-10-12 11:25 ` [dpdk-dev] [PATCH 1/2] mbuf: fix missing Tx offload flag name and list update Ferruh Yigit
2018-10-16 12:45 ` [dpdk-dev] [PATCH v2 " Jerin Jacob
2018-10-16 12:45 ` [dpdk-dev] [PATCH v2 2/2] mbuf: fix missing Tx outer UDP checksum flag name Jerin Jacob
2018-10-16 13:42 ` [dpdk-dev] [PATCH v2 1/2] mbuf: fix missing Tx offload flag name and list update Ferruh Yigit
2018-10-16 13:55 ` Ferruh Yigit [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=139362d2-a40a-f23d-99a7-142e02265ef8@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Jerin.JacobKollanukkaran@cavium.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=olivier.matz@6wind.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).