From: Andrew Morton <akpm@osdl.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Manfred Spraul <manfred@colorfullife.com>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [RFC 4/7] Move files_cachep to file.h
Date: Tue, 21 Nov 2006 00:09:02 -0800 [thread overview]
Message-ID: <20061121000902.52849f2f.akpm@osdl.org> (raw)
In-Reply-To: <20061118054403.8884.32124.sendpatchset@schroedinger.engr.sgi.com>
On Fri, 17 Nov 2006 21:44:03 -0800 (PST)
Christoph Lameter <clameter@sgi.com> wrote:
> Move files_cachep to file.h
>
> The proper place is in file.h since its related to file I/O.
>
> Signed-off-by: Christoph Lameter <clameter@sgi.com>
>
> Index: linux-2.6.19-rc5-mm2/include/linux/file.h
> ===================================================================
> --- linux-2.6.19-rc5-mm2.orig/include/linux/file.h 2006-11-15 16:48:08.583913536 -0600
> +++ linux-2.6.19-rc5-mm2/include/linux/file.h 2006-11-17 23:03:59.254839099 -0600
> @@ -101,4 +101,6 @@ struct files_struct *get_files_struct(st
> void FASTCALL(put_files_struct(struct files_struct *fs));
> void reset_files_struct(struct task_struct *, struct files_struct *);
>
> +extern kmem_cache_t *files_cachep;
> +
> #endif /* __LINUX_FILE_H */
> Index: linux-2.6.19-rc5-mm2/include/linux/slab.h
> ===================================================================
> --- linux-2.6.19-rc5-mm2.orig/include/linux/slab.h 2006-11-17 23:03:55.587532089 -0600
> +++ linux-2.6.19-rc5-mm2/include/linux/slab.h 2006-11-17 23:03:59.268512148 -0600
> @@ -298,7 +298,6 @@ static inline void kmem_set_shrinker(kme
>
> /* System wide caches */
> extern kmem_cache_t *names_cachep;
> -extern kmem_cache_t *files_cachep;
> extern kmem_cache_t *filp_cachep;
> extern kmem_cache_t *fs_cachep;
>
Please convert to `struct kmem_cache' (all patches).
--
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:[~2006-11-21 8:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 5:43 [RFC 0/7] Remove slab cache declarations in slab.h Christoph Lameter
2006-11-18 5:43 ` [RFC 1/7] Remove declaration of sighand_cachep from slab.h Christoph Lameter
2006-11-18 6:27 ` Stephen Rothwell
2006-11-20 16:20 ` Christoph Lameter
2006-11-21 8:07 ` Andrew Morton
2006-11-21 19:36 ` Christoph Lameter
2006-11-21 19:49 ` Andrew Morton
2006-11-21 19:56 ` Christoph Lameter
2006-11-21 20:07 ` Andrew Morton
2006-11-18 5:43 ` [RFC 2/7] Remove bio_cachep " Christoph Lameter
2006-11-18 5:43 ` [RFC 3/7] Move vm_area_cachep to mm.h Christoph Lameter
2006-11-18 5:44 ` [RFC 4/7] Move files_cachep to file.h Christoph Lameter
2006-11-21 8:09 ` Andrew Morton [this message]
2006-11-18 5:44 ` [RFC 5/7] Use external declaration for filep_cachep Christoph Lameter
2006-11-18 6:31 ` Stephen Rothwell
2006-11-20 16:20 ` Christoph Lameter
2006-11-18 5:44 ` [RFC 6/7] Use an external declaration in exit.c for fs_cachep Christoph Lameter
2006-11-18 6:32 ` Stephen Rothwell
2006-11-20 16:21 ` Christoph Lameter
2006-11-18 5:44 ` [RFC 7/7] Move names_cachep to fs.h Christoph Lameter
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=20061121000902.52849f2f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=penberg@cs.helsinki.fi \
/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