linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
	Andrew Paniakin <apanyaki@amazon.com>,
	Shuah Khan <shuah@kernel.org>,
	Brendan Higgins <brendan.higgins@linux.dev>,
	David Gow <davidgow@google.com>,
	damon@lists.linux.dev, linux-mm@kvack.org,
	linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] damon/{self,kunit}tests: minor fixups for DAMON debugfs interface tests
Date: Mon, 28 Oct 2024 16:30:52 -0700	[thread overview]
Message-ID: <20241028233058.283381-1-sj@kernel.org> (raw)

Fixup small broken window panes in DAMON selftests and kunit tests.

First four patches clean up DAMON debugfs interface selftests output, by
fixing segmentation fault of a test program (patch 1), removing
unnecessary debugging messages (patch 2), and hiding error messages from
expected failures (patches 3 and 4).

Following two patches fix copy-paste mistakes in DAMON Kconfig help
message that copied from debugfs kunit test (patch 5) and a comment on
the debugfs kunit test code (patch 6).

Signed-off-by: SeongJae Park <sj@kernel.org>

Andrew Paniakin (1):
  selftests/damon/huge_count_read_write: provide sufficiently large
    buffer for DEPRECATED file read

SeongJae Park (5):
  selftests/damon/huge_count_read_write: remove unnecessary debugging
    message
  selftests/damon/_debugfs_common: hide expected error message from
    test_write_result()
  selftests/damon/debugfs_duplicate_context_creation: hide errors from
    expected file write failures
  mm/damon/Kconfig: update DBGFS_KUNIT prompt copy for SYSFS_KUNIT
  mm/damon/tests/dbgfs-kunit: fix the header double inclusion guarding
    ifdef comment

 mm/damon/Kconfig                                           | 2 +-
 mm/damon/tests/dbgfs-kunit.h                               | 2 +-
 tools/testing/selftests/damon/_debugfs_common.sh           | 7 ++++++-
 .../selftests/damon/debugfs_duplicate_context_creation.sh  | 2 +-
 tools/testing/selftests/damon/huge_count_read_write.c      | 4 +---
 5 files changed, 10 insertions(+), 7 deletions(-)


base-commit: 13583c750117b4e10cdaf5578dcc7723b305ce4e
-- 
2.39.5



             reply	other threads:[~2024-10-28 23:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 23:30 SeongJae Park [this message]
2024-10-28 23:30 ` [PATCH 1/6] selftests/damon/huge_count_read_write: provide sufficiently large buffer for DEPRECATED file read SeongJae Park
2024-10-28 23:30 ` [PATCH 2/6] selftests/damon/huge_count_read_write: remove unnecessary debugging message SeongJae Park
2024-10-28 23:30 ` [PATCH 3/6] selftests/damon/_debugfs_common: hide expected error message from test_write_result() SeongJae Park
2024-10-28 23:30 ` [PATCH 4/6] selftests/damon/debugfs_duplicate_context_creation: hide errors from expected file write failures SeongJae Park
2024-10-28 23:30 ` [PATCH 5/6] mm/damon/Kconfig: update DBGFS_KUNIT prompt copy for SYSFS_KUNIT SeongJae Park
2024-10-28 23:30 ` [PATCH 6/6] mm/damon/tests/dbgfs-kunit: fix the header double inclusion guarding ifdef comment SeongJae Park

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=20241028233058.283381-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=apanyaki@amazon.com \
    --cc=brendan.higgins@linux.dev \
    --cc=damon@lists.linux.dev \
    --cc=davidgow@google.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shuah@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