From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rasesh Mody <rasesh.mody@cavium.com>, dev@dpdk.org
Cc: Harish Patil <harish.patil@cavium.com>, Dept-EngDPDKDev@cavium.com
Subject: Re: [dpdk-dev] [PATCH 1/3] net/qede: fix supported packet types
Date: Mon, 23 Oct 2017 11:35:51 -0700 [thread overview]
Message-ID: <ed2b4f68-5005-c249-f9a8-d14aef249b27@intel.com> (raw)
In-Reply-To: <1508375611-9326-1-git-send-email-rasesh.mody@cavium.com>
On 10/18/2017 6:13 PM, Rasesh Mody wrote:
> From: Harish Patil <harish.patil@cavium.com>
>
> Update/fix supported ptypes to return both inner and outer headers,
> tunnel_type, fragmented and VLAN packet types.
>
> Fixes: 3d4bb4411683 ("net/qede: add fastpath support for VXLAN tunneling")
> Fixes: 2ea6f76aff40 ("qede: add core driver")
>
> Signed-off-by: Harish Patil <harish.patil@cavium.com>
> Signed-off-by: Rasesh Mody <rasesh.mody@cavium.com>
Series applied to dpdk-next-net/master, thanks.
(There was a build error [1], fixed while applying, please check it.)
[1]
.../dpdk/drivers/net/qede/qede_ethdev.c: In function ‘qede_vxlan_tunn_config’:
.../dpdk/drivers/net/qede/qede_ethdev.c:684:13: error: ‘ucast.vlan’ may be used
uninitialized in this function [-Werror=maybe-uninitialized]
ucast->vlan == tmp->vlan &&
~~~~~^~~~~~
.../dpdk/drivers/net/qede/qede_ethdev.c:685:13: error: ‘ucast.vni’ may be used
uninitialized in this function [-Werror=maybe-uninitialized]
ucast->vni == tmp->vni)
~~~~~^~~~~
Fixed in patch 2/3, by providing initial value of "0" to ucast.
prev parent reply other threads:[~2017-10-23 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 1:13 Rasesh Mody
2017-10-19 1:13 ` [dpdk-dev] [PATCH 2/3] net/qede: add support for VXLAN UDP port config over VF Rasesh Mody
2017-10-19 1:13 ` [dpdk-dev] [PATCH 3/3] net/qede: fix to re-enable LRO during device start Rasesh Mody
2017-10-23 18:35 ` 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=ed2b4f68-5005-c249-f9a8-d14aef249b27@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=dev@dpdk.org \
--cc=harish.patil@cavium.com \
--cc=rasesh.mody@cavium.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).