linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Liew Rui Yan <aethernet65535@gmail.com>
Cc: SeongJae Park <sj@kernel.org>, damon@lists.linux.dev, linux-mm@kvack.org
Subject: Re: [PATCH v2 0/2] mm/damon: reset thread status parameters upon kdamond termination
Date: Fri, 17 Apr 2026 07:00:05 -0700	[thread overview]
Message-ID: <20260417140006.78938-1-sj@kernel.org> (raw)
In-Reply-To: <20260417042701.4077-1-aethernet65535@gmail.com>

On Fri, 17 Apr 2026 12:27:01 +0800 Liew Rui Yan <aethernet65535@gmail.com> wrote:

> On Thu, 16 Apr 2026 18:12:28 -0700 SeongJae Park <sj@kernel.org> wrote:
> 
> > Maybe I suggested too much...  If we decide to take both my suggested commit
> > description and the above change direction, maybe it is difficult to say you
> > are the main author who should be primarily responsible for any followup issues
> > on the patch.  Of course you will still deserve to have credits.  Maybe
> > 'Co-developed-by:'?
> 
> Yes, I've decide to adopt both your suggested commit description and the
> implementation. Therefore, since you've done the most of the work, you
> should be the main author of this patch.
> 
> > 
> > Meanwhile, I feel like the fix of this bug is taking bit unnecessarily long
> > time...
> 
> My apologies. I have had limited bandwidth recently.

That's not your fault!

> 
> > 
> > If you agree, hence, I'd like to take this over from this point, and finish up
> > the remaining works for this patch.  If you also agree, I will also take the
> > responsibility (authorship) from you, while keeping keep your credits with
> > 'Co-developed-by:' tag.  What do you think?
> 
> I agree to hand over this patch to you. Thank you for your help.

Thank you for generously accepting my suggestion, Liew.  I will do the
remaining works.

> 
> > 
> > By the way, I hope I'm not making you to get me wrong.  I'm not trying to steal
> > your credit (authorship).  In my opinion the authorship means the
> > responsibility (or, who to blame) more than the credit.  Putting right name to
> > the place for the responsibility is important for the long term maintenance and
> > evolvement of the community and the product (Linux) in my opinion, so I have to
> > say this.
> 
> Thank you for your explanation. I understand your point that authorship
> implies responsibility, and since most of the core ideas for this patch
> came from you, I fully agree that you should be the main author.

Again, appreciate generously understanding this.  Please don't forget there is
no change to your credit.  Without your contribution, the fix was impossible.


Thanks,
SJ

[...]


  reply	other threads:[~2026-04-17 14:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 18:52 Liew Rui Yan
2026-04-13 18:52 ` [PATCH v2 1/2] mm/damon/lru_sort: " Liew Rui Yan
2026-04-13 19:54   ` (sashiko review) " Liew Rui Yan
2026-04-13 18:52 ` [PATCH v2 2/2] mm/damon/reclaim: " Liew Rui Yan
2026-04-13 19:57   ` (sashiko review) " Liew Rui Yan
2026-04-13 22:05 ` [PATCH v2 0/2] mm/damon: " Liew Rui Yan
2026-04-14  0:28   ` SeongJae Park
2026-04-14  0:22 ` SeongJae Park
2026-04-14  0:34   ` SeongJae Park
2026-04-15 18:45     ` Liew Rui Yan
2026-04-15 23:55       ` SeongJae Park
2026-04-16  6:28         ` SeongJae Park
2026-04-17  1:12           ` SeongJae Park
2026-04-17  4:27             ` Liew Rui Yan
2026-04-17 14:00               ` SeongJae Park [this message]
2026-04-16  0:17 ` 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=20260417140006.78938-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=aethernet65535@gmail.com \
    --cc=damon@lists.linux.dev \
    --cc=linux-mm@kvack.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