From: Stephen Hemminger <stephen@networkplumber.org>
To: Moti Haimovsky <motih@mellanox.com>
Cc: gaetan.rivet@6wind.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH V2 1/2] net/failsafe: convert to new Tx offloads API
Date: Thu, 4 Jan 2018 12:15:13 -0800 [thread overview]
Message-ID: <20180104121513.0c654f10@xeon-e3> (raw)
In-Reply-To: <1515095458-186363-2-git-send-email-motih@mellanox.com>
On Thu, 4 Jan 2018 21:50:57 +0200
Moti Haimovsky <motih@mellanox.com> wrote:
> .tx_offload_capa = 0x0,
> + .tx_queue_offload_capa = 0x0,
> .flow_type_rss_offloads = 0x0,
Minor nit
you don't need to initialize every structure element.
Compiler defaults everything to zero.
next prev parent reply other threads:[~2018-01-04 20:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 19:31 [dpdk-dev] [PATCH 0/2] net/failsafe: convert to new ethdev " Moti Haimovsky
2018-01-04 19:31 ` [dpdk-dev] [PATCH 1/2] net/failsafe: convert to new Tx " Moti Haimovsky
2018-01-04 19:50 ` [dpdk-dev] [PATCH V2 0/2] net/failsafe: convert to new ethdev " Moti Haimovsky
2018-01-04 19:50 ` [dpdk-dev] [PATCH V2 1/2] net/failsafe: convert to new Tx " Moti Haimovsky
2018-01-04 20:15 ` Stephen Hemminger [this message]
2018-01-10 14:40 ` [dpdk-dev] [PATCH V3 " Moti Haimovsky
2018-01-10 14:40 ` [dpdk-dev] [PATCH V3 2/2] net/failsafe: convert to new Rx " Moti Haimovsky
2018-01-15 16:02 ` Gaëtan Rivet
2018-01-15 15:57 ` [dpdk-dev] [PATCH V3 1/2] net/failsafe: convert to new Tx " Gaëtan Rivet
2018-01-17 14:30 ` [dpdk-dev] [PATCH v4 1/2] net/failsafe: use " Moti Haimovsky
2018-01-17 14:30 ` [dpdk-dev] [PATCH v4 2/2] net/failsafe: use new Rx " Moti Haimovsky
2018-01-17 17:30 ` [dpdk-dev] [PATCH v4 1/2] net/failsafe: use new Tx " Gaëtan Rivet
2018-01-17 19:24 ` Ferruh Yigit
2018-01-04 19:50 ` [dpdk-dev] [PATCH V2 2/2] net/failsafe: convert to new Rx " Moti Haimovsky
2018-01-04 19:31 ` [dpdk-dev] [PATCH " Moti Haimovsky
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=20180104121513.0c654f10@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.com \
--cc=motih@mellanox.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).