From: Daniel Walter <dwalter@sigma-star.at>
To: linux-mtd@lists.infradead.org
Cc: richard@nod.at
Subject: [PATCH v2] mkfs.ubifs: fix compiler warning for WITHOUT_LZO
Date: Thu, 12 Nov 2015 12:52:09 +0100 [thread overview]
Message-ID: <20151112115209.GA2876@dw-nb.local> (raw)
Fix compiler warning about an unused variable.
ubifs-utils/mkfs.ubifs/compr.c:41:27: warning: ‘c’ defined but not used [-Wunused-variable]
static struct ubifs_info *c = &info_;
Signed-off-by: Daniel Walter <dwalter@sigma-star.at>
---
Changes since v1:
* added exact compiler warning to commit message as requested
---
ubifs-utils/mkfs.ubifs/compr.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/ubifs-utils/mkfs.ubifs/compr.c b/ubifs-utils/mkfs.ubifs/compr.c
index d534f10..8eff186 100644
--- a/ubifs-utils/mkfs.ubifs/compr.c
+++ b/ubifs-utils/mkfs.ubifs/compr.c
@@ -38,7 +38,9 @@
static void *lzo_mem;
static unsigned long long errcnt = 0;
+#ifndef WITHOUT_LZO
static struct ubifs_info *c = &info_;
+#endif
#define DEFLATE_DEF_LEVEL Z_DEFAULT_COMPRESSION
#define DEFLATE_DEF_WINBITS 11
--
2.6.2
next reply other threads:[~2015-11-12 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 11:52 Daniel Walter [this message]
2015-11-12 18:22 ` [PATCH v2] mkfs.ubifs: fix compiler warning for WITHOUT_LZO Brian Norris
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=20151112115209.GA2876@dw-nb.local \
--to=dwalter@sigma-star.at \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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).