DAMON development mailing list
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: SJ Park <sj@kernel.org>,
	stable@vger.kernel.org, damon@lists.linux.dev,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 7.2.y] mm/damon/core: skip aging from repeated aggressive merging
Date: Thu, 10 Sep 2026 06:50:26 -0700	[thread overview]
Message-ID: <20260910135026.168722-1-sj@kernel.org> (raw)
In-Reply-To: <2026091032-outright-varsity-64d9@gregkh>

On Thu, 10 Sep 2026 08:15:05 +0200 Greg KH <greg@kroah.com> wrote:

> On Wed, Sep 09, 2026 at 06:02:09PM -0700, SJ Park wrote:
> > On Wed, 9 Sep 2026 14:19:27 +0200 Greg KH <greg@kroah.com> wrote:
> > [...]
> > > Does not apply to the latest 7.2.y queue :(
> > 
> > Thank you, just rebased the patch to 7.2.5-rc1 and posted as another reply [1].
> > 
> > As number of stable patches for DAMON is increasing, this kind of patch
> > applying-order based conflict might be even more common in future.  Maybe I
> > could reduce this kind of issues if I could post fixed patches as single patch
> > series, instead of replying to this kind of individual failure report.
> > 
> > I was initially worried if your workflow is dependent to the guided workflow
> > (replying ported patch as a reply to each failure report), and hence if this
> > could make your job more difficult.  But I know the stable patch submission
> > rules are quite flexible.  And you may already have good enough automation for
> > such small change.s  So as long as I keep the essential stable patches rule
> > (use 'cherry-pick -x' option and add target branch name as patch subject tag),
> > that might not really make your work worse?
> 
> A patch series is great, and much simpler for me to apply, otherwise I
> have to just guess and go by the email date/time stamp to order them.

Thank you, I will try this next time.


Thanks,
SJ

[...]

  reply	other threads:[~2026-09-10 13:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2026090839-reoccupy-dizzy-a7bd@gregkh>
2026-09-09  4:34 ` [PATCH 7.2.y] mm/damon/core: skip aging from repeated aggressive merging SJ Park
2026-09-09  4:49   ` sashiko-bot
2026-09-09 12:19   ` Greg KH
2026-09-10  1:02     ` SJ Park
2026-09-10  6:15       ` Greg KH
2026-09-10 13:50         ` SJ Park [this message]
2026-09-10  0:52 ` SJ Park
2026-09-11 11:20   ` Sasha Levin

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=20260910135026.168722-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=damon@lists.linux.dev \
    --cc=greg@kroah.com \
    --cc=stable@vger.kernel.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