From: Andrew Morton <akpm@linux-foundation.org>
To: SeongJae Park <sj@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] DAMON fixes
Date: Mon, 15 Nov 2021 19:42:43 -0800 [thread overview]
Message-ID: <20211115194243.8faa12c3a9fdf881eb498d7a@linux-foundation.org> (raw)
In-Reply-To: <20211110145758.16558-1-sj@kernel.org>
On Wed, 10 Nov 2021 14:57:56 +0000 SeongJae Park <sj@kernel.org> wrote:
> This patchset fixes bugs in DAMON. Those cannot cleanly applied on
> v5.15.y. I will back-port these on v5.15.y and post later once these
> are merged in the mainline.
Thanks. I added cc:stable to these even though they won't apply. I
think that fits Greg's processes better.
prev parent reply other threads:[~2021-11-16 3:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 14:57 SeongJae Park
2021-11-10 14:57 ` [PATCH 1/2] mm/damon/dbgfs: Use '__GFP_NOWARN' for user-specified size buffer allocation SeongJae Park
2021-11-10 14:57 ` [PATCH 2/2] mm/damon/dbgfs: Fix missed use of damon_dbgfs_lock SeongJae Park
2021-11-16 3:42 ` Andrew Morton [this message]
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=20211115194243.8faa12c3a9fdf881eb498d7a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sj@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