linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
	Josh Law <objecting@objecting.org>,
	"Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
Cc: Josh Law <hlcj1234567@gmail.com>, SeongJae Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	damon@lists.linux.dev, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Kees Cook <kees@kernel.org>, Greg KH <gregkh@linuxfoundation.org>,
	Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH] mm/damon: introduce DAMON-based NUMA memory tiering module
Date: Mon, 30 Mar 2026 09:50:59 +0200	[thread overview]
Message-ID: <6deb290e-b168-4de2-95f8-fc784ed31c27@kernel.org> (raw)
In-Reply-To: <11429699-81b4-4c1e-b247-480136fd1faf@kernel.org>

On 30/03/2026 08:27, David Hildenbrand (Arm) wrote:
> On 3/27/26 16:22, Josh Law wrote:
>>
>>
>>>
>>> Josh,
>>>
>>> in general we try to be a welcoming upstream community. Finding people
>>> that are willing to work on the low-level bits and stick around is rare.
>>>
>>> At the same time, we need people that are willing to get familiar with
>>> the code base and technology, so they can help out with review and
>>> provide long-term value to the project. AI use is only partially useful
>>> in that context. Certainly not for writing patches as a newbie. At best,
>>> to double-check your understanding (e.g., AI review), help you learn
>>> (e.g., explore the code base), or improve your writing if your English
>>> is really, really bad.
>>>
>>> I prefer someone trying to use their own words to compose a change log
>>> and actually learn something on the way over some AI slop that reads
>>> nicer any day. Often, when you write a changelog you actually realize
>>> which corner cases you might be missing, that the design might be overly
>>> complicated, that, maybe, the reasoning or motivation is bad etc. It
>>> takes time but you actually learn something and are forced to think
>>> (crazy, right?).
>>>
>>> The same is particularly true when it comes to writing documentation, as
>>> people raised earlier in other context.
>>>
>>> Having that said, your actions made a lot of people's alarms go off and
>>> there is pretty much 0 trust now. As Lorenzo says, even now we are not
>>> really sure if you are saying the truth right now, which is a big problem.
>>>
>>> If you are, in fact, a real person, and are passionate to work on the
>>> kernel, it would be best if you would start things very slowly and don't
>>> use any AI for crafting your patches (including patch descriptions).
>>> Stick to one subsystem and ask people what good starting tasks/projects
>>> could be.
>>>
>>> Ideally, you'd find someone people trust around here, that can verify
>>> your identity (i.e., have a video chat etc) and start mentoring you on
>>> how to start working in the kernel community and gain trust.
>>>
>>> Now, I am still not sure whether I am talking to a bot here (there are
>>> too many things Lorenzo points out above that are very suspicious), but
>>> I just wanted to say that there are ways to become a trusted
>>> contributor, and that information might be useful for other people that
>>> might be interested in working on the kernel.
>>>
>>> It's certainly not by flooding the list with AI slop.
>>>
>>
>>
>> Hello david, thanks for being polite about this whole thing!
>>
>>
>> so, you are talking to a real human, i promise you that now
> 
> That's exactly, what I would say if I were a bot ;)
> 
> As a first step, fix the line wrapping. The following document was
> helpful to me in the past:
> 
> 	Documentation/process/email-clients.rst

Yeah, good luck. Several people asked for that already, like 10 or 20
times. Andrew asked that a few times.

And yesterday we got another sloppy posting, so that would be it for
having some time off to learn things and take slowly. 3 days after this
AI slop which does not even build.

Best regards,
Krzysztof


  reply	other threads:[~2026-03-30  7:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26  7:27 Josh Law
2026-03-26 10:34 ` Lorenzo Stoakes (Oracle)
2026-03-26 12:12   ` Krzysztof Kozlowski
2026-03-26 12:29     ` Lorenzo Stoakes (Oracle)
2026-03-26 12:40       ` Krzysztof Kozlowski
2026-03-26 12:50         ` Lorenzo Stoakes (Oracle)
2026-03-26 15:14           ` Josh Law
2026-03-26 15:43             ` Krzysztof Kozlowski
2026-03-26 16:10               ` Josh Law
2026-03-26 16:33                 ` Lorenzo Stoakes (Oracle)
2026-03-26 16:39                   ` Josh Law
2026-03-27  4:09                     ` SeongJae Park
2026-03-27  8:37                     ` David Hildenbrand (Arm)
2026-03-27 15:22                       ` Josh Law
2026-03-30  6:27                         ` David Hildenbrand (Arm)
2026-03-30  7:50                           ` Krzysztof Kozlowski [this message]
2026-03-30  8:16                             ` David Hildenbrand (Arm)
2026-03-30 10:14                               ` Herbert
2026-03-30 10:36                                 ` David Hildenbrand (Arm)
2026-03-30 10:41                                   ` Herbert
2026-03-30 10:43                                   ` Herbert
2026-03-30 11:56                                     ` Vlastimil Babka
2026-03-30 10:40                           ` Herbert
2026-03-27 12:50 ` kernel test robot
2026-03-27 17:45 ` kernel test robot

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=6deb290e-b168-4de2-95f8-fc784ed31c27@kernel.org \
    --to=krzk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=david@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hlcj1234567@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=objecting@objecting.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