From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] e2fsprogs: fix trivial build warnings
Date: Sat, 18 Jul 2009 14:04:13 -0400 [thread overview]
Message-ID: <20090718180413.GA2416@mit.edu> (raw)
In-Reply-To: <4A5D2BED.30009@redhat.com>
On Tue, Jul 14, 2009 at 08:07:57PM -0500, Eric Sandeen wrote:
> Quite a lot of warnings have crept into the build; this fixes
> many of the trivial ones. Mostly unused variables, a
> couple of header file inclusions, and one missing return
> value.
>
> There are a few other warnings that I'll send patches for
> in a bit.
Most of these ones I had fixed in the e2fsprogs maint branch already,
except for this one:
diff --git a/misc/mke2fs.c b/misc/mke2fs.c
index a9b01cb..e10fd35 100644
--- a/misc/mke2fs.c
+++ b/misc/mke2fs.c
@@ -20,6 +20,7 @@
#include <stdio.h>
#include <string.h>
+#include <strings.h>
#include <fcntl.h>
#include <ctype.h>
#include <time.h>
... which was in one of Val's patches as well, but for the life of me
I can't figure out what warnings it's supposed to suppress. It
doesn't make a difference for me, and we're not using any of the
traditional functions which would be defined in strings.h as opposed
to string.h (i.e., bcopy, et. al.)
I assume this must be a Fedora header file thing? What difference
does it make for you?
- Ted
next prev parent reply other threads:[~2009-07-18 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 1:07 [PATCH] e2fsprogs: fix trivial build warnings Eric Sandeen
2009-07-18 18:04 ` Theodore Tso [this message]
2009-07-18 18:11 ` Eric Sandeen
2009-07-18 22:32 ` Theodore Tso
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=20090718180413.GA2416@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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).