From: Christoph Lameter <cl@linux.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the slab tree
Date: Tue, 15 Mar 2011 12:45:21 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1103151119200.5754@router.home> (raw)
In-Reply-To: <20110314200247.92ae2bd7.sfr@canb.auug.org.au>
On Mon, 14 Mar 2011, Stephen Rothwell wrote:
> mm/slub.c: In function 'slab_free':
> mm/slub.c:2124: warning: label 'redo' defined but not used
>
> Introduced by commit 8a5ec0ba42c4 ("Lockless (and preemptless) fastpaths
> for slub").
---
Subject: slub: Dont define useless label in the !CONFIG_CMPXCHG_LOCAL case
The redo label needs #ifdeffery.
Signed-off-by: Christoph Lameter <cl@linux.com>
mm/slub.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Index: linux-next/mm/slub.c
===================================================================
--- linux-next.orig/mm/slub.c 2011-03-15 12:41:41.000000000 -0500
+++ linux-next/mm/slub.c 2011-03-15 12:43:06.000000000 -0500
@@ -2119,9 +2119,11 @@ static __always_inline void slab_free(st
#ifndef CONFIG_CMPXCHG_LOCAL
local_irq_save(flags);
-#endif
+#else
redo:
+#endif
+
/*
* Determine the currently cpus per cpu slab.
* The cpu may change afterward. However that does not matter since
next prev parent reply other threads:[~2011-03-15 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 9:02 Stephen Rothwell
2011-03-15 17:45 ` Christoph Lameter [this message]
2012-07-12 5:51 Stephen Rothwell
2024-07-15 7:06 Stephen Rothwell
2024-07-15 8:46 ` Vlastimil Babka
2024-09-06 8:33 Stephen Rothwell
2024-09-06 9:27 ` Vlastimil Babka
2026-01-14 4:13 Stephen Rothwell
2026-01-14 9:51 ` Vlastimil Babka
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=alpine.DEB.2.00.1103151119200.5754@router.home \
--to=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=sfr@canb.auug.org.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®