* [PATCH] mm/memcontrol.c: fix the placement of 'MAX_NUMNODES > 1' if block
@ 2014-12-06 16:04 Fabio Estevam
2014-12-07 10:29 ` Michal Hocko
0 siblings, 1 reply; 2+ messages in thread
From: Fabio Estevam @ 2014-12-06 16:04 UTC (permalink / raw)
To: akpm; +Cc: hannes, mhocko, linux-mm, Fabio Estevam
From: Fabio Estevam <fabio.estevam@freescale.com>
When building ARM allmodconfig we get the following build warning:
mm/memcontrol.c:1629:13: warning: 'test_mem_cgroup_node_reclaimable' defined but not used [-Wunused-function]
As test_mem_cgroup_node_reclaimable() is only used inside the
'#if MAX_NUMNODES > 1' block, we should also place its definition there as well.
Reported-by: Olof's autobuilder <build@lixom.net>
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index c6ac50e..d538b08 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -1616,6 +1616,7 @@ static void mem_cgroup_out_of_memory(struct mem_cgroup *memcg, gfp_t gfp_mask,
NULL, "Memory cgroup out of memory");
}
+#if MAX_NUMNODES > 1
/**
* test_mem_cgroup_node_reclaimable
* @memcg: the target memcg
@@ -1638,7 +1639,6 @@ static bool test_mem_cgroup_node_reclaimable(struct mem_cgroup *memcg,
return false;
}
-#if MAX_NUMNODES > 1
/*
* Always updating the nodemask is not very good - even if we have an empty
--
1.9.1
--
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>
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] mm/memcontrol.c: fix the placement of 'MAX_NUMNODES > 1' if block
2014-12-06 16:04 [PATCH] mm/memcontrol.c: fix the placement of 'MAX_NUMNODES > 1' if block Fabio Estevam
@ 2014-12-07 10:29 ` Michal Hocko
0 siblings, 0 replies; 2+ messages in thread
From: Michal Hocko @ 2014-12-07 10:29 UTC (permalink / raw)
To: Fabio Estevam; +Cc: akpm, hannes, linux-mm, Fabio Estevam
Hi,
this has been fixed last week already
http://marc.info/?l=linux-mm&m=141751847710864&w=2
Thanks!
On Sat 06-12-14 14:04:43, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> When building ARM allmodconfig we get the following build warning:
>
> mm/memcontrol.c:1629:13: warning: 'test_mem_cgroup_node_reclaimable' defined but not used [-Wunused-function]
>
> As test_mem_cgroup_node_reclaimable() is only used inside the
> '#if MAX_NUMNODES > 1' block, we should also place its definition there as well.
>
> Reported-by: Olof's autobuilder <build@lixom.net>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
> mm/memcontrol.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index c6ac50e..d538b08 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1616,6 +1616,7 @@ static void mem_cgroup_out_of_memory(struct mem_cgroup *memcg, gfp_t gfp_mask,
> NULL, "Memory cgroup out of memory");
> }
>
> +#if MAX_NUMNODES > 1
> /**
> * test_mem_cgroup_node_reclaimable
> * @memcg: the target memcg
> @@ -1638,7 +1639,6 @@ static bool test_mem_cgroup_node_reclaimable(struct mem_cgroup *memcg,
> return false;
>
> }
> -#if MAX_NUMNODES > 1
>
> /*
> * Always updating the nodemask is not very good - even if we have an empty
> --
> 1.9.1
>
--
Michal Hocko
SUSE Labs
--
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>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-12-07 10:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-06 16:04 [PATCH] mm/memcontrol.c: fix the placement of 'MAX_NUMNODES > 1' if block Fabio Estevam
2014-12-07 10:29 ` Michal Hocko
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox