From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-mm@kvack.org
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: linux-next: Tree for August 25 (mm/slub)
Date: Wed, 25 Aug 2010 09:45:59 -0700 [thread overview]
Message-ID: <20100825094559.bc652afe.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100825132057.c8416bef.sfr@canb.auug.org.au>
On Wed, 25 Aug 2010 13:20:57 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100824:
2 separate slub build errors/warnings:
mm/slub.c:1732: error: implicit declaration of function 'slab_pre_alloc_hook'
mm/slub.c:1751: error: implicit declaration of function 'slab_post_alloc_hook'
mm/slub.c:1881: error: implicit declaration of function 'slab_free_hook'
mm/slub.c:1886: error: implicit declaration of function 'slab_free_hook_irq'
and in different builds:
mm/slub.c:1898: note: expected 'struct kmem_cache *' but argument is of type 'struct kmem_cache **'
mm/slub.c:1756: note: expected 'struct kmem_cache *' but argument is of type 'struct kmem_cache **'
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-mm@kvack.org
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: linux-next: Tree for August 25 (mm/slub)
Date: Wed, 25 Aug 2010 09:45:59 -0700 [thread overview]
Message-ID: <20100825094559.bc652afe.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100825132057.c8416bef.sfr@canb.auug.org.au>
On Wed, 25 Aug 2010 13:20:57 +1000 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100824:
2 separate slub build errors/warnings:
mm/slub.c:1732: error: implicit declaration of function 'slab_pre_alloc_hook'
mm/slub.c:1751: error: implicit declaration of function 'slab_post_alloc_hook'
mm/slub.c:1881: error: implicit declaration of function 'slab_free_hook'
mm/slub.c:1886: error: implicit declaration of function 'slab_free_hook_irq'
and in different builds:
mm/slub.c:1898: note: expected 'struct kmem_cache *' but argument is of type 'struct kmem_cache **'
mm/slub.c:1756: note: expected 'struct kmem_cache *' but argument is of type 'struct kmem_cache **'
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-08-25 16:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 3:20 linux-next: Tree for August 25 Stephen Rothwell
2010-08-25 16:45 ` Randy Dunlap [this message]
2010-08-25 16:45 ` linux-next: Tree for August 25 (mm/slub) Randy Dunlap
2010-08-25 19:07 ` Christoph Lameter
2010-08-25 19:07 ` Christoph Lameter
2010-08-25 20:30 ` Randy Dunlap
2010-08-25 20:30 ` Randy Dunlap
2010-08-26 18:17 ` Pekka Enberg
2010-08-26 18:17 ` Pekka Enberg
2010-08-25 23:18 ` David Rientjes
2010-08-25 23:18 ` David Rientjes
2010-08-25 19:11 ` Christoph Lameter
2010-08-25 19:11 ` Christoph Lameter
2010-08-25 19:21 ` Randy Dunlap
2010-08-25 19:51 ` Christoph Lameter
2010-08-25 20:13 ` Randy Dunlap
2010-08-25 20:13 ` Randy Dunlap
2010-08-26 18:17 ` Pekka Enberg
2010-08-26 18:17 ` Pekka Enberg
2010-08-25 23:32 ` David Rientjes
2010-08-25 23:32 ` David Rientjes
2010-08-26 1:31 ` Christoph Lameter
2010-08-26 1:31 ` Christoph Lameter
2010-08-26 18:17 ` Pekka Enberg
2010-08-26 18:17 ` 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=20100825094559.bc652afe.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.