[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdXyJhaFUbKX2Hhoa2y4hVK+0NhvL4hNL_8RnVOxaCkq=g@mail.gmail.com>
Date: Tue, 10 Jun 2025 18:41:43 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Andrew Morton <akpm@...ux-foundation.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
Hi Andrew,
On Tue, 10 Jun 2025 at 17:54, Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Tue, 10 Jun 2025 11:05:40 +0200 Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> > 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.
Just revert the commit?
Distros are (usually) not using defconfig files anyway.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists