From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [wireless-next:for-davem 13/261] drivers/net/ethernet/broadcom/tg3.c:7783:40: sparse: Using plain in
Date: Wed, 03 Oct 2012 01:12:32 +0000 [thread overview]
Message-ID: <20121003011232.GA8750@localhost> (raw)
Hi Michael,
FYI, there are new sparse warnings show up in
tree: git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next.git for-davem
head: e4d680c706284ca0413a84bd2a28fda76b360904
commit: 49a359e31762f798f3abef00c7d6b807a644eadf [13/261] tg3: Introduce separate functions to allocate/free RX/TX rings.
drivers/net/ethernet/broadcom/tg3.c:787:5: sparse: symbol 'tg3_ape_scratchpad_read' was not declared. Should it be static?
+ drivers/net/ethernet/broadcom/tg3.c:7783:40: sparse: Using plain integer as NULL pointer
drivers/net/ethernet/broadcom/tg3.c:10209:38: sparse: bad constant expression
vim +7783 drivers/net/ethernet/broadcom/tg3.c
49a359e3 drivers/net/ethernet/broadcom/tg3.c (Michael Chan 2012-09-28 7782) if (tg3_flag(tp, ENABLE_RSS)) {
49a359e3 drivers/net/ethernet/broadcom/tg3.c (Michael Chan 2012-09-28 @7783) u16 *prodptr = 0;
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu, Yuanhan Liu Intel Corporation
reply other threads:[~2012-10-03 1:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121003011232.GA8750@localhost \
--to=fengguang.wu@intel.com \
--cc=kernel-janitors@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