From: Stephen Hemminger <stephen@networkplumber.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: [PATCH net-next 0/7] warning related fixes
Date: Tue, 10 Jan 2017 10:18:09 -0800 [thread overview]
Message-ID: <20170110181816.18991-1-sthemmin@microsoft.com> (raw)
These are all patches to fix other warnings found while cleaning
up netvsc driver.
Stephen Hemminger (7):
flow_dissector: make local function static
vxlan: remove unused variable
socket: make sockfs_setattr static
dcb: validate netlink attribute link
tcp_nv: make tcpnv_get_info static
ipv6: make udpv6_queue_rcv_skb static
fq_codel: fix set never used warning
drivers/net/vxlan.c | 3 +--
net/core/flow_dissector.c | 4 ++--
net/dcb/dcbnl.c | 11 +++++++----
net/ipv4/tcp_nv.c | 4 ++--
net/ipv6/udp.c | 2 +-
net/sched/sch_fq_codel.c | 2 --
net/socket.c | 2 +-
7 files changed, 14 insertions(+), 14 deletions(-)
--
2.11.0
next reply other threads:[~2017-01-10 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 18:18 Stephen Hemminger [this message]
2017-01-10 18:18 ` [PATCH net-next 1/7] flow_dissector: make local function static Stephen Hemminger
2017-01-10 18:32 ` David Miller
2017-01-10 18:43 ` Stephen Hemminger
2017-01-10 18:18 ` [PATCH net-next 2/7] vxlan: remove unused variable Stephen Hemminger
2017-01-10 18:18 ` [PATCH net-next 3/7] socket: make sockfs_setattr static Stephen Hemminger
2017-01-10 18:18 ` [PATCH net-next 4/7] dcb: validate netlink attribute link Stephen Hemminger
2017-01-10 18:18 ` [PATCH net-next 5/7] tcp_nv: make tcpnv_get_info static Stephen Hemminger
2017-01-10 19:50 ` Lawrence Brakmo
2017-01-10 18:18 ` [PATCH net-next 6/7] ipv6: make udpv6_queue_rcv_skb static Stephen Hemminger
2017-01-10 18:18 ` [PATCH net-next 7/7] fq_codel: fix set never used warning Stephen Hemminger
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=20170110181816.18991-1-sthemmin@microsoft.com \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.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).