From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Roland Dreier <roland@purestorage.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Tatyana Nikolova <Tatyana.E.Nikolova@intel.com>
Subject: linux-next: build warnings in Linus' tree
Date: Thu, 4 Jul 2013 14:58:52 +1000 [thread overview]
Message-ID: <20130704145852.44975d5801f592d00807d1c0@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
Hi all,
Building Linus' tree, today's linux-next build (x86_64 allmodconfig)
produced this warning (these have been around for a while):
drivers/infiniband/hw/nes/nes_hw.c:81:23: warning: 'nes_iwarp_state_str' defined but not used [-Wunused-variable]
static unsigned char *nes_iwarp_state_str[] = {
^
drivers/infiniband/hw/nes/nes_hw.c:92:23: warning: 'nes_tcp_state_str' defined but not used [-Wunused-variable]
static unsigned char *nes_tcp_state_str[] = {
^
Introduced by commit bca1935ccdec ("RDMA/nes: Fix compilation error when
nes_debug is enabled").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-07-04 4:59 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 4:58 Stephen Rothwell [this message]
2013-07-09 21:48 ` linux-next: build warnings in Linus' tree Nikolova, Tatyana E
-- strict thread matches above, loose matches on Subject: below --
2022-06-14 6:57 Stephen Rothwell
2022-05-26 7:21 Stephen Rothwell
2022-01-27 4:30 Stephen Rothwell
2022-01-27 6:01 ` Christoph Hellwig
2022-01-27 16:44 ` Stephen Rothwell
2022-01-27 4:24 Stephen Rothwell
2021-11-22 22:44 Stephen Rothwell
2021-11-23 7:04 ` Borislav Petkov
2021-11-05 5:03 Stephen Rothwell
2021-10-12 10:56 Stephen Rothwell
2021-10-12 20:13 ` Randy Dunlap
2021-10-08 5:47 Stephen Rothwell
2021-10-10 21:27 ` Stephen Rothwell
2021-10-11 20:42 ` Rob Herring
2021-10-12 14:39 ` Arnd Bergmann
2021-10-13 22:12 ` Anatolij Gustschin
2021-10-13 22:17 ` Rob Herring
2021-10-13 22:28 ` Anatolij Gustschin
2021-10-13 23:22 ` Rob Herring
2021-10-14 8:44 ` Arnd Bergmann
2021-10-14 12:24 ` Anatolij Gustschin
2020-09-07 23:11 Stephen Rothwell
2020-09-08 13:14 ` Josh Poimboeuf
2020-09-09 0:15 ` Stephen Rothwell
2020-04-03 22:19 Stephen Rothwell
2020-04-03 23:16 ` Rob Herring
2020-04-03 23:31 ` Nicolas Saenz Julienne
2017-11-13 21:52 Stephen Rothwell
2017-11-13 22:03 ` Linus Torvalds
2011-08-15 1:57 Stephen Rothwell
2011-05-23 1:25 Stephen Rothwell
2011-05-23 2:31 ` Eduardo Silva
2011-01-14 0:17 Stephen Rothwell
2011-01-14 0:09 Stephen Rothwell
2011-01-14 0:17 ` Andrew Morton
2011-01-14 1:06 ` Greg KH
2010-08-17 1:24 Stephen Rothwell
2010-08-30 1:42 ` Stephen Rothwell
2010-08-30 6:08 ` Zhang Rui
2010-09-03 2:01 ` Stephen Rothwell
2010-09-03 2:36 ` Len Brown
2010-09-17 4:26 ` Stephen Rothwell
2010-09-27 13:31 ` Stephen Rothwell
2010-08-07 2:21 Stephen Rothwell
2010-08-07 8:13 ` Vikas Chaudhary
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=20130704145852.44975d5801f592d00807d1c0@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Tatyana.E.Nikolova@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=roland@purestorage.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).