The patch titled
Subject: memcg: mark memcg1_events static const
has been added to the -mm tree. Its filename is
memcg-mark-memcg1_events-static-const.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/memcg-mark-memcg1_events-static-const.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/memcg-mark-memcg1_events-static-const.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Greg Thelen <gthelen@xxxxxxxxxx>
Subject: memcg: mark memcg1_events static const
Mark memcg1_events static: it's only used by memcontrol.c. And mark it
const: it's not modified.
Link: http://lkml.kernel.org/r/20180503192940.94971-1-gthelen@xxxxxxxxxx
Signed-off-by: Greg Thelen <gthelen@xxxxxxxxxx>
Acked-by: Michal Hocko <mhocko@xxxxxxxx>
Cc: Johannes Weiner <hannes@xxxxxxxxxxx>
Cc: Vladimir Davydov <vdavydov.dev@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/memcontrol.c~memcg-mark-memcg1_events-static-const mm/memcontrol.c
--- a/mm/memcontrol.c~memcg-mark-memcg1_events-static-const
+++ a/mm/memcontrol.c
@@ -3088,7 +3088,7 @@ static int memcg_numa_stat_show(struct s
#endif /* CONFIG_NUMA */
/* Universal VM events cgroup1 shows, original sort order */
-unsigned int memcg1_events[] = {
+static const unsigned int memcg1_events[] = {
PGPGIN,
PGPGOUT,
PGFAULT,
_
Patches currently in -mm which might be from gthelen@xxxxxxxxxx are
memcg-mark-memcg1_events-static-const.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
