From: David Rientjes <rientjes@google.com>
To: Yuanchu Xie <yuanchu@google.com>
Cc: Shuah Khan <shuah@kernel.org>, Markus Boehme <markubo@amazon.de>,
SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] selftests/damon: add damon to selftests root Makefile
Date: Sun, 24 Apr 2022 12:35:14 -0700 (PDT) [thread overview]
Message-ID: <93c3f9b4-7e14-858b-bf6c-23e4f3bec232@google.com> (raw)
In-Reply-To: <20220418202017.3583638-1-yuanchu@google.com>
On Mon, 18 Apr 2022, Yuanchu Xie wrote:
> Currently the damon selftests are not built with the rest of the
> selftests. We add damon to the list of targets.
>
> Fixes: b348eb7abd09 ("mm/damon: add user space selftests")
> Reviewed-by: SeongJae Park <sj@kernel.org>
> Signed-off-by: Yuanchu Xie <yuanchu@google.com>
Acked-by: David Rientjes <rientjes@google.com>
next prev parent reply other threads:[~2022-04-24 19:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 20:20 [PATCH RESEND] selftests/damon: add damon to selftests root Makefile Yuanchu Xie
2022-04-24 19:35 ` David Rientjes [this message]
2022-04-25 19:37 ` Shuah Khan
2022-04-25 20:03 ` Shuah Khan
2022-05-04 0:03 ` [PATCH v2 1/2] selftests/damon: suppress compiler warnings for huge_count_read_write Yuanchu Xie
2022-05-04 0:03 ` [PATCH v2 2/2] selftests/damon: add damon to selftests root Makefile Yuanchu Xie
2022-05-04 0:16 ` SeongJae Park
2022-05-04 4:50 ` David Rientjes
2022-05-04 0:11 ` [PATCH v2 1/2] selftests/damon: suppress compiler warnings for huge_count_read_write SeongJae Park
2022-05-04 18:29 ` [PATCH v3] " Yuanchu Xie
2022-05-04 18:32 ` Yuanchu Xie
2022-05-04 18:45 ` SeongJae Park
2022-05-04 22:12 ` Yuanchu Xie
2022-05-17 1:07 ` Yuanchu Xie
2022-05-17 16:04 ` SeongJae Park
2022-05-25 0:55 ` Yuanchu Xie
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=93c3f9b4-7e14-858b-bf6c-23e4f3bec232@google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=markubo@amazon.de \
--cc=shuah@kernel.org \
--cc=sj@kernel.org \
--cc=yuanchu@google.com \
/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;
as well as URLs for NNTP newsgroup(s).