All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: stable@vger.kernel.org
Cc: SeongJae Park <sj@kernel.org>, damon@lists.linux.dev, linux-mm@kvack.org
Subject: [PATCH 5.15.y 0/2] fix issue in damon_va_evenly_split_region()
Date: Fri,  6 Dec 2024 10:16:18 -0800	[thread overview]
Message-ID: <20241206181620.91603-1-sj@kernel.org> (raw)
In-Reply-To: <2024120625-recycling-till-0cca@gregkh>

The fix depends on 044cd9750fe0 ("mm/damon/vaddr-test: split a test
function having >1024 bytes frame size"), which is not on 5.15.y tree.
Even after applying it, the fix might not cleanly cherry-picked due to
the file path change that seems not automatically detected on every
setup[1].  Since my setup somehow automatically detects the file path
change and do cherry-pick cleanly, posting both patches to avoid
unnecessary delay.

[1] https://lore.kernel.org/20241206173426.75223-1-sj@kernel.org

SeongJae Park (1):
  mm/damon/vaddr-test: split a test function having >1024 bytes frame
    size

Zheng Yejian (1):
  mm/damon/vaddr: fix issue in damon_va_evenly_split_region()

 mm/damon/vaddr-test.h | 78 +++++++++++++++++++++++--------------------
 mm/damon/vaddr.c      |  4 +--
 2 files changed, 43 insertions(+), 39 deletions(-)

-- 
2.39.5


  reply	other threads:[~2024-12-06 18:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 10:16 FAILED: patch "[PATCH] mm/damon/vaddr: fix issue in damon_va_evenly_split_region()" failed to apply to 5.15-stable tree gregkh
2024-12-06 18:16 ` SeongJae Park [this message]
2024-12-06 18:16   ` [PATCH 5.15.y 1/2] mm/damon/vaddr-test: split a test function having >1024 bytes frame size SeongJae Park
2024-12-06 20:30     ` David Laight
2024-12-07  2:07     ` Sasha Levin
2024-12-06 18:16   ` [PATCH 5.15.y 2/2] mm/damon/vaddr: fix issue in damon_va_evenly_split_region() SeongJae Park
2024-12-07  2:07     ` 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=20241206181620.91603-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-mm@kvack.org \
    --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 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.