From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: SeongJae Park <sj@kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y 1/2] mm/damon/vaddr-test: split a test function having >1024 bytes frame size
Date: Fri, 6 Dec 2024 21:07:19 -0500 [thread overview]
Message-ID: <20241206190233-bf977b9dc275a34b@stable.kernel.org> (raw)
In-Reply-To: <20241206181620.91603-2-sj@kernel.org>
[ Sasha's backport helper bot ]
Hi,
Found matching upstream commit: 044cd9750fe010170f5dc812e4824d98f5ea928c
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (exact SHA1)
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
1: 044cd9750fe01 ! 1: 2de5dba01c393 mm/damon/vaddr-test: split a test function having >1024 bytes frame size
@@ Commit message
Cc: Shuah Khan <shuah@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
+ (cherry picked from commit 044cd9750fe010170f5dc812e4824d98f5ea928c)
## mm/damon/vaddr-test.h ##
@@ mm/damon/vaddr-test.h: static void damon_test_apply_three_regions4(struct kunit *test)
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2024-12-07 2:07 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 ` [PATCH 5.15.y 0/2] fix issue in damon_va_evenly_split_region() SeongJae Park
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 [this message]
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=20241206190233-bf977b9dc275a34b@stable.kernel.org \
--to=sashal@kernel.org \
--cc=sj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox