[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E7311A37-F5D9-4248-A51A-9B105A49A923@lca.pw>
Date: Tue, 17 Dec 2019 10:17:10 -0500
From: Qian Cai <cai@....pw>
To: Michal Hocko <mhocko@...nel.org>
Cc: Chris Down <chris@...isdown.name>,
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 10:13 AM, Michal Hocko <mhocko@...nel.org> wrote:
>
> I do understand the general purpose of the warning. I am simply not sure
> the kernel tree is a good candidate with a huge number of different
> config combinations that might easily result in warnings which would
> tend to result in even more ifdeferry than we have.
Yes, compiling test without real-world use case is evil. Once we ignore the evil, it becomes much more manageable.
Powered by blists - more mailing lists