From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Andrew Morton <akpm@linux-foundation.org>,
SeongJae Park <sj@kernel.org>, Honggyu Kim <honggyu.kim@sk.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Additional MM updates for 6.16-rc1
Date: Tue, 10 Jun 2025 11:05:40 +0200 [thread overview]
Message-ID: <CAMuHMdU1NdNjx3f1V9j2FACWwC5faPKCXChtW6Z=i2JyXquFuA@mail.gmail.com> (raw)
In-Reply-To: <20250601151222.60ead71e7d8492a18c711a05@linux-foundation.org>
Hi Andrew et al,
On Mon, 2 Jun 2025 at 17:55, Andrew Morton <akpm@linux-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")).
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-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
next prev parent reply other threads:[~2025-06-10 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 22:12 Andrew Morton
2025-06-02 15:05 ` Matthew Wilcox
2025-06-02 19:17 ` Andrew Morton
2025-06-02 19:20 ` Matthew Wilcox
2025-06-02 23:03 ` Linus Torvalds
2025-06-10 9:05 ` Geert Uytterhoeven [this message]
2025-06-10 15:54 ` Andrew Morton
2025-06-10 16:41 ` Geert Uytterhoeven
2025-06-10 17:04 ` SeongJae Park
2025-06-10 17:27 ` Linus Torvalds
2025-06-10 17:32 ` SeongJae Park
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMuHMdU1NdNjx3f1V9j2FACWwC5faPKCXChtW6Z=i2JyXquFuA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=honggyu.kim@sk.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=sj@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox