[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200109114055.67bda2b70d92b07ef13e3047@linux-foundation.org>
Date: Thu, 9 Jan 2020 11:40:55 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Roman Gushchin <guro@...com>
Cc: <linux-mm@...ck.org>, Michal Hocko <mhocko@...nel.org>,
Johannes Weiner <hannes@...xchg.org>,
Shakeel Butt <shakeelb@...gle.com>,
Vladimir Davydov <vdavydov.dev@...il.com>,
<linux-kernel@...r.kernel.org>, <kernel-team@...com>
Subject: Re: [PATCH 1/7] mm: kmem: remove duplicate definitions of
__memcg_kmem_(un)charge()
On Thu, 9 Jan 2020 09:27:39 -0800 Roman Gushchin <guro@...com> wrote:
> For some reason these inline functions are defined twice. Remove
> the second identical copy.
Don't think so - that wouldn't have compiled.
> --- a/include/linux/memcontrol.h
> +++ b/include/linux/memcontrol.h
> @@ -1438,15 +1438,6 @@ static inline void memcg_kmem_uncharge(struct page *page, int order)
> {
> }
>
> -static inline int __memcg_kmem_charge(struct page *page, gfp_t gfp, int order)
> -{
> - return 0;
> -}
> -
> -static inline void __memcg_kmem_uncharge(struct page *page, int order)
> -{
> -}
> -
> #define for_each_memcg_cache_index(_idx) \
> for (; NULL; )
>
Maybe you confused these with memcg_kmem_charge() and
memcg_kmem_uncharge()?
Powered by blists - more mailing lists