From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: build issue for v2.6.25-rc7-187-ga9edadb in mm/slub.c
Date: Tue, 1 Apr 2008 09:47:45 +0200 [thread overview]
Message-ID: <200804010947.48205.toralf.foerster@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0803311146280.6510@schroedinger.engr.sgi.com>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
At Monday 31 March 2008 20:47:32 Christoph Lameter wrote :
> Does this fix things?
>
>
Yes :-)
> Subject: Fix undefined count_partial of !CONFIG_SLABINFO
>
> Typo in the check if we need the count_partial function that was
> introduced by 53625b4204753b904addd40ca96d9ba802e6977d
>
> Signed-off-by: Christoph Lameter <clameter@sgi.com>
>
> ---
> mm/slub.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-2.6/mm/slub.c
> ===================================================================
> --- linux-2.6.orig/mm/slub.c 2008-03-31 11:29:28.000000000 -0700
> +++ linux-2.6/mm/slub.c 2008-03-31 11:32:23.000000000 -0700
> @@ -2688,7 +2688,7 @@ void kfree(const void *x)
> }
> EXPORT_SYMBOL(kfree);
>
> -#if defined(SLUB_DEBUG) || defined(CONFIG_SLABINFO)
> +#if defined(CONFIG_SLUB_DEBUG) || defined(CONFIG_SLABINFO)
> static unsigned long count_partial(struct kmem_cache_node *n)
> {
> unsigned long flags;
>
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-04-01 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 12:59 Toralf Förster
2008-03-31 18:47 ` Christoph Lameter
2008-04-01 7:47 ` Toralf Förster [this message]
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=200804010947.48205.toralf.foerster@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=clameter@sgi.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®