From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/7] nfs-utils: Use -Werror warning flags to clean up the code.
Date: Tue, 20 Feb 2018 13:50:27 -0500 [thread overview]
Message-ID: <20180220185034.26301-1-steved@redhat.com> (raw)
I received a patch that tried to turns on some
of these -Werror flags but could not get passed
the warning that were being generated by
the rpcgen code.
After taking care of the rpcgen warnings, I
took over the patch and finished it off.
The warning flags I choose to use are pattern
after the list in the libostree and the
systemd list.
Steve Dickson (7):
configure.ac: clean up
Removed missing-prototypes warnings.
Removed format-overflow=2 warnings
Removed format=2 warnings
Removed undef warnings
Removed missing-include-dirs warnings
Added more -Werror= warning flags
configure.ac | 41 ++++++++++++++++++++++++--------------
support/misc/mountpoint.c | 1 +
support/nfs/atomicio.c | 2 ++
support/nfs/cacheio.c | 2 +-
support/nfs/closeall.c | 2 ++
support/nfs/rpcmisc.c | 1 +
support/nfs/strlcat.c | 2 ++
support/nfs/strlcpy.c | 2 ++
support/nfs/svc_socket.c | 2 ++
support/nfs/wildmat.c | 7 +++++++
support/nfsidmap/libnfsidmap.c | 3 ++-
support/nfsidmap/nfsidmap_plugin.h | 1 +
support/nfsidmap/nss.c | 2 +-
systemd/systemd.c | 1 +
utils/blkmapd/device-discovery.c | 10 +++++-----
utils/blkmapd/dm-device.c | 2 +-
utils/gssd/Makefile.am | 2 ++
utils/gssd/err_util.c | 1 +
utils/gssd/gss_names.c | 1 +
utils/gssd/gssd_proc.c | 4 ++--
utils/gssd/krb5_util.c | 6 +++---
utils/gssd/svcgssd.c | 4 ++--
utils/gssd/svcgssd_mech2file.c | 1 +
utils/idmapd/Makefile.am | 2 ++
utils/idmapd/idmapd.c | 4 ++--
utils/mount/configfile.c | 4 ++++
utils/mount/mount_libmount.c | 2 ++
utils/mount/stropts.c | 2 ++
utils/mountd/svc_run.c | 1 +
utils/nfsdcltrack/sqlite.c | 3 ++-
utils/nfsidmap/Makefile.am | 2 ++
utils/nfsstat/nfsstat.c | 4 +++-
utils/statd/svc_run.c | 1 +
33 files changed, 90 insertions(+), 35 deletions(-)
--
2.14.3
next reply other threads:[~2018-02-20 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 18:50 Steve Dickson [this message]
2018-02-20 18:50 ` [PATCH 1/7] configure.ac: clean up Steve Dickson
2018-02-20 18:50 ` [PATCH 2/7] Removed missing-prototypes warnings Steve Dickson
2018-02-20 18:50 ` [PATCH 3/7] Removed format-overflow=2 warnings Steve Dickson
2018-02-20 18:50 ` [PATCH 4/7] Removed format=2 warnings Steve Dickson
2018-02-20 18:50 ` [PATCH 5/7] Removed undef warnings Steve Dickson
2018-02-20 18:50 ` [PATCH 6/7] Removed missing-include-dirs warnings Steve Dickson
2018-02-20 18:50 ` [PATCH 7/7] Added more -Werror= warning flags Steve Dickson
2018-02-23 14:21 ` [PATCH 0/7] nfs-utils: Use -Werror warning flags to clean up the code Steve Dickson
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=20180220185034.26301-1-steved@redhat.com \
--to=steved@redhat.com \
--cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.