[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5D853968-99FD-4B66-9784-C1C540B23F92@lca.pw>
Date: Tue, 17 Dec 2019 10:09:33 -0500
From: Qian Cai <cai@....pw>
To: Chris Down <chris@...isdown.name>
Cc: Michal Hocko <mhocko@...nel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
Johannes Weiner <hannes@...xchg.org>,
Vladimir Davydov <vdavydov.dev@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
cgroups@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm: memcontrol.c: move mem_cgroup_id_get_many under CONFIG_MMU
> On Dec 17, 2019, at 9:37 AM, Chris Down <chris@...isdown.name> wrote:
>
> I struggle to imagine a real issue this would catch that wouldn't already be caught by other means. If it's just the risks of dead code, that seems equally risky as taking time away from reviewers.
Hate to say this but ignore unrealistic configs compiling test should not take that much time.
Powered by blists - more mailing lists