From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 0/5] remove double parenthesis
Date: Thu, 14 Dec 2017 15:32:16 -0800 [thread overview]
Message-ID: <20171214233221.30928-1-stephen@networkplumber.org> (raw)
Noticed in ethdev an obvious case of extra parenthesis so
went hunting for others as well. There seems to be some weird
coding standard that loves extra parenthesis (or developers
don't understand basic C precedence rules).
Stephen Hemminger (5):
bnx2x: remove (redundant) parenthesis
kni: remove (redundant) parenthesis
ethdev: remove (redundant) parenthesis
distributor: remove (unnecessary) parenthesis
loadbalancer: remove (unnecessary) parenthesis
drivers/net/bnx2x/bnx2x.c | 2 +-
drivers/net/bnx2x/ecore_sp.c | 4 ++--
examples/load_balancer/config.c | 2 +-
lib/librte_distributor/rte_distributor.c | 2 +-
lib/librte_eal/linuxapp/kni/ethtool/igb/igb_main.c | 4 ++--
lib/librte_eal/linuxapp/kni/ethtool/ixgbe/ixgbe_common.c | 6 +++---
lib/librte_ether/rte_ethdev.c | 4 ++--
7 files changed, 12 insertions(+), 12 deletions(-)
--
2.11.0
next reply other threads:[~2017-12-14 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 23:32 Stephen Hemminger [this message]
2017-12-14 23:32 ` [dpdk-dev] [PATCH 1/5] bnx2x: remove (redundant) parenthesis Stephen Hemminger
2017-12-14 23:32 ` [dpdk-dev] [PATCH 2/5] kni: " Stephen Hemminger
2017-12-14 23:32 ` [dpdk-dev] [PATCH 3/5] ethdev: " Stephen Hemminger
2017-12-14 23:32 ` [dpdk-dev] [PATCH 4/5] distributor: remove (unnecessary) parenthesis Stephen Hemminger
2017-12-14 23:32 ` [dpdk-dev] [PATCH 5/5] loadbalancer: " Stephen Hemminger
2018-01-05 21:09 ` [dpdk-dev] [PATCH 0/5] remove double parenthesis 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=20171214233221.30928-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@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).