From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, shr@devkernel.io, david@redhat.com,
adobriyan@gmail.com, akpm@linux-foundation.org
Subject: [merged mm-hotfixes-stable] proc-fix-smaps_rollup-test-after-ksm-changes.patch removed from -mm tree
Date: Tue, 19 Sep 2023 13:22:08 -0700 [thread overview]
Message-ID: <20230919202208.AF51BC433C9@smtp.kernel.org> (raw)
The quilt patch titled
Subject: selftests/proc: fixup proc-empty-vm test after KSM changes
has been removed from the -mm tree. Its filename was
proc-fix-smaps_rollup-test-after-ksm-changes.patch
This patch was dropped because it was merged into the mm-hotfixes-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Alexey Dobriyan <adobriyan@gmail.com>
Subject: selftests/proc: fixup proc-empty-vm test after KSM changes
Date: Thu, 7 Sep 2023 14:10:12 +0300
/proc/${pid}/smaps_rollup is not empty file even if process's address
space is empty, update the test.
Link: https://lkml.kernel.org/r/725e041f-e9df-4f3d-b267-d4cd2774a78d@p183
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: Stefan Roesch <shr@devkernel.io>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
tools/testing/selftests/proc/proc-empty-vm.c | 1 +
1 file changed, 1 insertion(+)
--- a/tools/testing/selftests/proc/proc-empty-vm.c~proc-fix-smaps_rollup-test-after-ksm-changes
+++ a/tools/testing/selftests/proc/proc-empty-vm.c
@@ -267,6 +267,7 @@ static const char g_smaps_rollup[] =
"Private_Dirty: 0 kB\n"
"Referenced: 0 kB\n"
"Anonymous: 0 kB\n"
+"KSM: 0 kB\n"
"LazyFree: 0 kB\n"
"AnonHugePages: 0 kB\n"
"ShmemPmdMapped: 0 kB\n"
_
Patches currently in -mm which might be from adobriyan@gmail.com are
extract-and-use-file_line-macro.patch
reply other threads:[~2023-09-19 20:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230919202208.AF51BC433C9@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=shr@devkernel.io \
/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.