From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: linux-next: build warnings after merge of the net tree
Date: Fri, 20 May 2016 13:33:30 +1000 [thread overview]
Message-ID: <20160520133330.12a1aa65@canb.auug.org.au> (raw)
Hi all,
After merging the net tree, today's linux-next build (arm
multi_v7_defconfig) produced these warnings:
drivers/net/usb/pegasus.c: In function 'read_bulk_callback':
drivers/net/usb/pegasus.c:475:1: warning: label 'goon' defined but not used [-Wunused-label]
goon:
^
drivers/net/usb/pegasus.c:446:8: warning: unused variable 'pkt_len' [-Wunused-variable]
__u16 pkt_len;
^
drivers/net/usb/pegasus.c:445:6: warning: unused variable 'buf' [-Wunused-variable]
u8 *buf = urb->transfer_buffer;
^
drivers/net/usb/pegasus.c:443:17: warning: unused variable 'count' [-Wunused-variable]
int rx_status, count = urb->actual_length;
^
Introduced by commit
e00be9e4d0ff ("net: pegasus: remove dead coding")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-05-20 3:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 3:33 Stephen Rothwell [this message]
2016-05-20 5:57 ` linux-next: build warnings after merge of the net tree David Miller
-- strict thread matches above, loose matches on Subject: below --
2022-04-11 4:36 Stephen Rothwell
2021-11-04 3:48 Stephen Rothwell
2011-08-12 1:53 Stephen Rothwell
2011-08-12 10:01 ` David Miller
2010-08-31 1:55 Stephen Rothwell
2010-08-31 4:56 ` David Miller
2010-09-01 1:25 ` Stephen Rothwell
2010-09-01 3:57 ` David Miller
2010-06-16 3:38 Stephen Rothwell
2010-06-16 4:52 ` David Miller
2010-06-16 6:30 ` Stephen Rothwell
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=20160520133330.12a1aa65@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xypron.glpk@gmx.de \
/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