All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.com>
To: Herbert <objecting@objecting.org>, david@kernel.org
Cc: krzk@kernel.org, ljs@kernel.org, hlcj1234567@gmail.com,
	sj@kernel.org, akpm@linux-foundation.org, damon@lists.linux.dev,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, kees@kernel.org,
	gregkh@linuxfoundation.org, brauner@kernel.org
Subject: Re: [PATCH] mm/damon: introduce DAMON-based NUMA memory tiering module
Date: Mon, 30 Mar 2026 13:56:32 +0200	[thread overview]
Message-ID: <f031418a-af79-41bb-96a9-2f88ea6ee3fd@suse.com> (raw)
In-Reply-To: <19d3e5747e1.83b0f66f64051.6129386944586321569@objecting.org>

On 3/30/26 12:43, Herbert wrote:
>> >
>> >
>> > ? That was me learning the ropes, by making a patch to the QCOM subsystem
>> >
>> >
>> > and it was a genuinely "ok" patch.
>> >
>> >
>> > May you please tell me what I did wrong here.
>> I thought you wanted to "take a couple months break"? And I suggested
>> getting a mentor first.
> 
> Yeah, that again, was a bit stupid of me, but sorry for breaking my break, but I wanted to try doing a human patch, to see if I am capable 
> 
> 
> 
> 
>> Anyhow, this mail was sent from "Herbert", which is quite ... confusing.
> 
>  
> Changed, it was a display name for some reason.

We've heard enough of your excuses that look less and less plausible. Just
go away at this point, please.

  reply	other threads:[~2026-03-30 11:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26  7:27 [PATCH] mm/damon: introduce DAMON-based NUMA memory tiering module 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
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 [this message]
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=f031418a-af79-41bb-96a9-2f88ea6ee3fd@suse.com \
    --to=vbabka@suse.com \
    --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=krzk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.