The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-kernel@vger.kernel.org
Cc: Vegard Nossum <vegard.nossum@gmail.com>,
	Eric B Munson <ebmunson@us.ibm.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Dave Airlie <airlied@linux.ie>
Subject: v2.6.31-7381-g7fa0772: new build warnings: kmemcheck, __deprecated, hugetlb, radeon
Date: Tue, 22 Sep 2009 18:34:16 +0200	[thread overview]
Message-ID: <4AB8FC88.8020608@s5r6.in-berlin.de> (raw)

Latest git compiles with extreme noise:

In file included from include/net/inet_connection_sock.h:23,
                  from include/linux/tcp.h:178,
                  from include/linux/ipv6.h:215,
                  from include/net/ipv6.h:16,
                  from include/linux/sunrpc/clnt.h:25,
                  from include/linux/nfs_fs.h:52,
                  from kernel/sysctl.c:48:
include/net/inet_sock.h: In function 'inet_reqsk_alloc':
include/net/inet_sock.h:208: warning: ISO C90 forbids mixed declarations 
and code

Vegard, this is obviously caused by commit 
45e3ff82708c65c895d5c5882aff17ecf62a80b5.

$ grep KMEMCH .config
CONFIG_HAVE_ARCH_KMEMCHECK=y

(I.e. CONFIG_KMEMCHECK is off.)

More kmemcheck bogosity:

   CC      net/core/skbuff.o
In file included from include/net/ip.h:30,
                  from include/linux/errqueue.h:27,
                  from net/core/skbuff.c:59:
include/net/inet_sock.h: In function 'inet_reqsk_alloc':
include/net/inet_sock.h:208: warning: ISO C90 forbids mixed declarations 
and code
net/core/skbuff.c: In function '__alloc_skb':
net/core/skbuff.c:205: warning: ISO C90 forbids mixed declarations and code
net/core/skbuff.c:206: warning: ISO C90 forbids mixed declarations and code
net/core/skbuff.c:227: warning: ISO C90 forbids mixed declarations and code
net/core/skbuff.c:228: warning: ISO C90 forbids mixed declarations and code
net/core/skbuff.c: In function 'skb_clone':
net/core/skbuff.c:645: warning: ISO C90 forbids mixed declarations and code
net/core/skbuff.c:646: warning: ISO C90 forbids mixed declarations and code


This one is older:

   CC      net/ethernet/eth.o
[...kmemcheck noise from inet_sock.h:208, and then...:]
net/ethernet/eth.c: At top level:
net/ethernet/eth.c:402: warning: 'print_mac' is deprecated (declared at 
net/ethernet/eth.c:398)
net/ethernet/eth.c:402: warning: 'print_mac' is deprecated (declared at 
net/ethernet/eth.c:398)

Obviously added by b5eb0589937eae2d58fca17fa45ed44152e772ed.
Johannes, can't the __deprecated logic be suppressed when print_mac is 
used in EXPORT_SYMBOL?


Next one:

   CC      mm/mmap.o
mm/mmap.c: In function 'do_mmap_pgoff':
mm/mmap.c:953: warning: unused variable 'user'

Eric, this was added by 4e52780d41a741fb4861ae1df2413dd816ec11b1.

$ grep HUGETLB .config
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set


Next one:

   CC [M]  drivers/gpu/drm/radeon/radeon_ttm.o
drivers/gpu/drm/radeon/radeon_ttm.c: In function 'radeon_ttm_debugfs_init':
drivers/gpu/drm/radeon/radeon_ttm.c:714: warning: unused variable 'i'
drivers/gpu/drm/radeon/radeon_ttm.c: At top level:
drivers/gpu/drm/radeon/radeon_ttm.c:692: warning: 
'radeon_mem_types_list' defined but not used
drivers/gpu/drm/radeon/radeon_ttm.c:693: warning: 
'radeon_mem_types_names' defined but not used

Dave, added by fa8a123855e20068204982596b8fafceb1a67f0b.

$ grep -e RADEON -e DEBUG_FS .config
CONFIG_DRM_RADEON=m
CONFIG_FB_RADEON=y
CONFIG_FB_RADEON_I2C=y
# CONFIG_FB_RADEON_BACKLIGHT is not set
# CONFIG_FB_RADEON_DEBUG is not set
# CONFIG_DEBUG_FS is not set

-- 
Stefan Richter
-=====-==--= =--= =-==-
http://arcgraph.de/sr/

             reply	other threads:[~2009-09-22 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 16:34 Stefan Richter [this message]
2009-09-23  6:39 ` v2.6.31-7381-g7fa0772: new build warnings: kmemcheck, __deprecated, hugetlb, radeon Johannes Berg
2009-09-23  7:19 ` Jean Delvare
2009-09-23  7:21   ` Pekka Enberg
2009-09-23 15:13     ` Stefan Richter
2009-09-23  8:19   ` Jean Delvare
2009-09-23  7:20 ` Pekka Enberg

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=4AB8FC88.8020608@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=airlied@linux.ie \
    --cc=ebmunson@us.ibm.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vegard.nossum@gmail.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