From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/2] Fixing a couple warnings
Date: Thu, 31 May 2018 11:55:23 -0400 [thread overview]
Message-ID: <20180531155525.60495-1-steved@redhat.com> (raw)
Here are a couple warnings that I started getting
when I compiled on a freshly install Fedora 28.
The first patch turns off the compiling of rpcgen
by default. The command produces code that cause
a number of warnings which are now errors.
The old glibc rpcgen, which is now in the
rpcsvc-proto package, does a much better job
of not creating warnings.
The second patch fixes a couple warnings I
was not seeing.
Steve Dickson (1):
rpcgen: Only compile the command when configured.
gabriele balducci (1):
Fixed format overflow warnings in mountd and nfsd
configure.ac | 2 +-
utils/mountd/mountd.c | 2 +-
utils/nfsd/nfsd.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--
2.17.0
next reply other threads:[~2018-05-31 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 15:55 Steve Dickson [this message]
2018-05-31 15:55 ` [PATCH 1/2] rpcgen: Only compile the command when configured Steve Dickson
2018-05-31 15:55 ` [PATCH 2/2] Fixed format overflow warnings in mountd and nfsd Steve Dickson
2018-06-05 17:20 ` [PATCH 0/2] Fixing a couple warnings 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=20180531155525.60495-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 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).