From: Christoph Lameter <cl@gentwo.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org
Subject: Re: [mmotm:master 74/230] mm/slab.h:299:10: error: 'struct kmem_cache' has no member named 'node'
Date: Fri, 20 Jun 2014 09:21:12 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.11.1406200916070.10271@gentwo.org> (raw)
In-Reply-To: <53a38f31.ttbTrpTZnPLPRHcz%fengguang.wu@intel.com>
Argh a SLOB configuration which does not use node specfic management data.
Subject: SLOB has no node specific management structures.
Do not provide the defintions for node management structures for SLOB.
Signed-off-by: Christoph Lameter <cl@linux.com>
Index: linux/mm/slab.h
===================================================================
--- linux.orig/mm/slab.h 2014-06-20 09:17:22.582566992 -0500
+++ linux/mm/slab.h 2014-06-20 09:19:00.803449284 -0500
@@ -262,7 +262,7 @@ static inline struct kmem_cache *cache_f
}
#endif
-
+#ifndef CONFIG_SLOB
/*
* The slab lists for all objects.
*/
@@ -307,5 +307,7 @@ static inline struct kmem_cache_node *ge
for (__node = 0; __n = get_node(__s, __node), __node < nr_node_ids; __node++) \
if (__n)
+#endif
+
void *slab_next(struct seq_file *m, void *p, loff_t *pos);
void slab_stop(struct seq_file *m, void *p);
--
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>
next prev parent reply other threads:[~2014-06-20 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 1:32 kbuild test robot
2014-06-20 14:21 ` Christoph Lameter [this message]
2014-07-01 1:08 ` David Rientjes
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.11.1406200916070.10271@gentwo.org \
--to=cl@gentwo.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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