From: Bart Van Assche <bvanassche@acm.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v2 0/5] Fix net/core W=1 warnings
Date: Mon, 25 Mar 2019 09:17:18 -0700 [thread overview]
Message-ID: <20190325161723.144556-1-bvanassche@acm.org> (raw)
Hi Dave,
This patch series addresses the compiler warnings reported when
building the code in net/core with W=1. Please consider this patch
series for kernel v5.2.
Thanks,
Bart.
Changes compared to v1:
- Dropped two patches from this series.
- Rebased this patch series on top of
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
Bart Van Assche (5):
net/core: Document reuseport_add_sock() bind_inany argument
net/core: Document all dev_ioctl() arguments
net/core: Document __skb_flow_dissect() flags argument
net/core: Fix rtnetlink kernel-doc headers
net/core: Allow the compiler to verify declaration and definition
consistency
net/core/datagram.c | 2 ++
net/core/datagram.h | 15 +++++++++++++++
net/core/dev_ioctl.c | 3 ++-
net/core/flow_dissector.c | 2 ++
net/core/rtnetlink.c | 9 ++++++---
net/core/skbuff.c | 5 ++---
net/core/sock_reuseport.c | 2 ++
7 files changed, 31 insertions(+), 7 deletions(-)
create mode 100644 net/core/datagram.h
--
2.21.0.155.ge902e9bcae20
next reply other threads:[~2019-03-25 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 16:17 Bart Van Assche [this message]
2019-03-25 16:17 ` [PATCH v2 1/5] net/core: Document reuseport_add_sock() bind_inany argument Bart Van Assche
2019-03-25 16:17 ` [PATCH v2 2/5] net/core: Document all dev_ioctl() arguments Bart Van Assche
2019-03-25 16:17 ` [PATCH v2 3/5] net/core: Document __skb_flow_dissect() flags argument Bart Van Assche
2019-03-25 16:17 ` [PATCH v2 4/5] net/core: Fix rtnetlink kernel-doc headers Bart Van Assche
2019-03-25 16:17 ` [PATCH v2 5/5] net/core: Allow the compiler to verify declaration and definition consistency Bart Van Assche
2019-03-25 18:26 ` Sabrina Dubroca
2019-03-26 17:11 ` Bart Van Assche
2019-03-26 23:50 ` Sabrina Dubroca
2019-03-26 18:17 ` Al Viro
2019-03-27 0:03 ` Sabrina Dubroca
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=20190325161723.144556-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).