* [2.6 patch] mm/memory.c: EXPORT_UNUSED_SYMBOL
@ 2006-06-30 11:32 Adrian Bunk
2006-07-01 3:35 ` Andrew Morton
0 siblings, 1 reply; 2+ messages in thread
From: Adrian Bunk @ 2006-06-30 11:32 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
This patch marks an unused export as EXPORT_UNUSED_SYMBOL.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.17-mm4-full/mm/memory.c.old 2006-06-30 02:51:59.000000000 +0200
+++ linux-2.6.17-mm4-full/mm/memory.c 2006-06-30 02:52:26.000000000 +0200
@@ -1863,7 +1863,7 @@
return 0;
}
-EXPORT_SYMBOL(vmtruncate_range);
+EXPORT_UNUSED_SYMBOL(vmtruncate_range); /* June 2006 */
/*
* Primitive swap readahead code. We simply read an aligned block of
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [2.6 patch] mm/memory.c: EXPORT_UNUSED_SYMBOL
2006-06-30 11:32 [2.6 patch] mm/memory.c: EXPORT_UNUSED_SYMBOL Adrian Bunk
@ 2006-07-01 3:35 ` Andrew Morton
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Morton @ 2006-07-01 3:35 UTC (permalink / raw)
To: Adrian Bunk; +Cc: linux-kernel, Hugh Dickins, Badari Pulavarty
On Fri, 30 Jun 2006 13:32:40 +0200
Adrian Bunk <bunk@stusta.de> wrote:
> -EXPORT_SYMBOL(vmtruncate_range);
> +EXPORT_UNUSED_SYMBOL(vmtruncate_range); /* June 2006 */
vmtruncate_range() is a sensible-looking API, but it's purely for
MADV_REMOVE and I don't think it's a thing we intended that filesystems be
using, and I don't think that it's a thing which we want to be supporting
as an export unless there's a good reason.
So yes, let's give this a try.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-07-01 3:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-30 11:32 [2.6 patch] mm/memory.c: EXPORT_UNUSED_SYMBOL Adrian Bunk
2006-07-01 3:35 ` Andrew Morton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox