[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191002075451.GG15624@dhcp22.suse.cz>
Date: Wed, 2 Oct 2019 09:54:51 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Nick Desaulniers <ndesaulniers@...gle.com>
Cc: Arnd Bergmann <arnd@...db.de>,
Johannes Weiner <hannes@...xchg.org>,
Vladimir Davydov <vdavydov.dev@...il.com>,
Qian Cai <cai@....pw>,
Andrew Morton <akpm@...ux-foundation.org>,
Roman Gushchin <guro@...com>,
Shakeel Butt <shakeelb@...gle.com>,
Chris Down <chris@...isdown.name>, Tejun Heo <tj@...nel.org>,
cgroups@...r.kernel.org,
Linux Memory Management List <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>
Subject: Re: [PATCH] mm/memcontrol.c: fix another unused function warning
On Tue 01-10-19 09:36:24, Nick Desaulniers wrote:
> On Tue, Oct 1, 2019 at 7:22 AM Arnd Bergmann <arnd@...db.de> wrote:
> >
> > Removing the mem_cgroup_id_get() stub function introduced a new warning
> > of the same kind when CONFIG_MMU is disabled:
> >
> > mm/memcontrol.c:4929:13: error: unused function 'mem_cgroup_id_get_many' [-Werror,-Wunused-function]
> >
> > Address this using a __maybe_unused annotation.
> >
> > Note: alternatively, this could be moved into an #ifdef block. Marking it
>
> Hi Arnd,
> Thank you for the patch! I would prefer to move the definition to the
> correct set of #ifdef guards rather than __maybe_unused. Maybe move
> the definition of mem_cgroup_id_get_many() to just before
> __mem_cgroup_clear_mc()? I find __maybe_unused to be a code smell.
Agreed!
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists