[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250610085416.062b4bc386dde2ea475369f5@linux-foundation.org>
Date: Tue, 10 Jun 2025 08:54:16 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: SeongJae Park <sj@...nel.org>, Honggyu Kim <honggyu.kim@...com>, Linus
Torvalds <torvalds@...ux-foundation.org>, linux-mm@...ck.org,
mm-commits@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Additional MM updates for 6.16-rc1
On Tue, 10 Jun 2025 11:05:40 +0200 Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> Hi Andrew et al,
>
> On Mon, 2 Jun 2025 at 17:55, Andrew Morton <akpm@...ux-foundation.org> wrote:
> > - The 2 patch series "mm/damon: build-enable essential DAMON components
> > by default" from SeongJae Park reworks DAMON Kconfig to make it easier
> > to enable CONFIG_DAMON.
>
> ... or, make it harder to disable it?
>
> Given no single defconfig file in v6.15 enables CONFIG_DAMON, I find
> it hard to believe defaulting DAMON to "y" is the right thing to do...
> (Yes, I have read the rationale in commit 28615e6eed152f2f
> ("mm/damon/Kconfig: enable CONFIG_DAMON by default")).
>
So what do you recommend? Editing all the defconfigs seems a bit lame.
Powered by blists - more mailing lists