From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-next@vger.kernel.org
Subject: linux-next: rr tree build warnings
Date: Thu, 8 Jan 2009 17:44:41 +1100 [thread overview]
Message-ID: <20090108174441.c5fc9371.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Hi Rusty,
Today's linux-next build (sparc32 defconfig) produced these new warnings
(I think they are down to the rr tree:
kernel/workqueue.c: In function 'current_is_keventd':
kernel/workqueue.c:742: warning: unused variable 'cpu'
That I have reported before.
mm/slab.c: In function 'start_cpu_timer':
mm/slab.c:865: warning: initialization from incompatible pointer type
mm/slab.c: At top level:
mm/slab.c:686: warning: 'reap_work' defined but not used
Not sure about that one.
net/xfrm/xfrm_ipcomp.c: In function 'ipcomp_decompress':
net/xfrm/xfrm_ipcomp.c:48: warning: unused variable 'cpu'
net/xfrm/xfrm_ipcomp.c: In function 'ipcomp_compress':
net/xfrm/xfrm_ipcomp.c:142: warning: unused variable 'cpu'
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-01-08 6:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 6:44 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-09 7:31 linux-next: rr tree build warnings Stephen Rothwell
2009-11-09 7:40 ` Stephen Rothwell
2009-11-10 2:20 ` Rusty Russell
2009-11-10 5:20 ` Sam Ravnborg
2009-11-10 2:20 ` Rusty Russell
2009-03-16 5:47 Stephen Rothwell
2009-01-06 3:43 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=20090108174441.c5fc9371.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.