From: wfg@linux.intel.com
To: kernel-janitors@vger.kernel.org
Subject: [slab:for-next 12/13] mm/slab_common.c:101:1: warning: label 'oops' defined but not used
Date: Wed, 11 Jul 2012 00:14:20 +0000 [thread overview]
Message-ID: <20120711001420.GA5556@localhost> (raw)
Hi Christoph,
There are new compile warnings show up in
tree: git://github.com/penberg/linux.git for-next
head: 737b719ed6569ffcd015fcdf3039dc7af47af877
commit: 20cea9683ecc6dd75a80c0dd02dc69c64e95be75 [12/13] mm, sl[aou]b: Move kmem_cache_create mutex handling to common code
All warnings:
mm/slab_common.c: In function 'kmem_cache_create':
mm/slab_common.c:101:1: warning: label 'oops' defined but not used [-Wunused-label]
The patch removed all references to oops: w/o removing the label
itself.
vim +101 mm/slab_common.c
98
99 s = __kmem_cache_create(name, size, align, flags, ctor);
100
> 101 oops:
102 mutex_unlock(&slab_mutex);
103 put_online_cpus();
104
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
reply other threads:[~2012-07-11 0:14 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=20120711001420.GA5556@localhost \
--to=wfg@linux.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