From: kbuild test robot <fengguang.wu@intel.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
kbuild-all@01.org
Subject: [next:master 191/463] mm/memcontrol.c:1074:19: sparse: symbol 'get_mem_cgroup_from_mm' was not declared. Should it be static?
Date: Sun, 23 Mar 2014 04:49:27 +0800 [thread overview]
Message-ID: <532df757.AkU5AH07Cpb86z5c%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 06ed26d1de59ce7cbbe68378b7e470be169750e5
commit: 83ab64d4c75418a019166519d2f95015868f79a4 [191/463] memcg: get_mem_cgroup_from_mm()
reproduce: make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> mm/memcontrol.c:1074:19: sparse: symbol 'get_mem_cgroup_from_mm' was not declared. Should it be static?
mm/slab.h:182:18: sparse: incompatible types in comparison expression (different address spaces)
mm/slab.h:182:18: sparse: incompatible types in comparison expression (different address spaces)
mm/slab.h:182:18: sparse: incompatible types in comparison expression (different address spaces)
mm/memcontrol.c:5562:21: sparse: incompatible types in comparison expression (different address spaces)
mm/memcontrol.c:5564:21: sparse: incompatible types in comparison expression (different address spaces)
mm/memcontrol.c:7015:31: sparse: incompatible types in comparison expression (different address spaces)
Please consider folding the attached diff :-)
---
0-DAY kernel build testing backend Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
[-- Attachment #2: make-it-static-83ab64d4c75418a019166519d2f95015868f79a4.diff --]
[-- Type: text/x-diff, Size: 864 bytes --]
From: Fengguang Wu <fengguang.wu@intel.com>
Subject: [PATCH next] memcg: get_mem_cgroup_from_mm() can be static
TO: Johannes Weiner <hannes@cmpxchg.org>
CC: cgroups@vger.kernel.org
CC: linux-mm@kvack.org
CC: linux-kernel@vger.kernel.org
CC: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 28fd509..bdb62eb 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -1071,7 +1071,7 @@ struct mem_cgroup *mem_cgroup_from_task(struct task_struct *p)
return mem_cgroup_from_css(task_css(p, mem_cgroup_subsys_id));
}
-struct mem_cgroup *get_mem_cgroup_from_mm(struct mm_struct *mm)
+static struct mem_cgroup *get_mem_cgroup_from_mm(struct mm_struct *mm)
{
struct mem_cgroup *memcg = NULL;
next reply other threads:[~2014-03-22 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 20:49 kbuild test robot [this message]
2014-03-24 16:30 ` Johannes Weiner
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=532df757.AkU5AH07Cpb86z5c%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--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