From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,balbirs@nvidia.com,brads@mainlining.org,akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] taskstats-drop-the-unused-cpu_dont_care-enum-member.patch removed from -mm tree
Date: Tue, 06 Oct 2026 19:05:10 -0700 [thread overview]
Message-ID: <20261007020511.4C9301F0089C@smtp.kernel.org> (raw)
The quilt patch titled
Subject: taskstats: drop the unused CPU_DONT_CARE enum member
has been removed from the -mm tree. Its filename was
taskstats-drop-the-unused-cpu_dont_care-enum-member.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Bradley Morgan <brads@mainlining.org>
Subject: taskstats: drop the unused CPU_DONT_CARE enum member
Date: Tue, 15 Sep 2026 18:06:23 +0000
CPU_DONT_CARE was added by the original listener cpumask code in 2006
(f9fd8914c1ac) and has never had a single user, not even in the
commit that introduced it. It survived every refactor of the listener
path since, including the recent handler folds.
Kill it, twenty years is enough.
Link: https://lore.kernel.org/20260915180623.22058-1-brads@mainlining.org
Signed-off-by: Bradley Morgan <brads@mainlining.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Balbir Singh <balbirs@nvidia.com>
---
kernel/taskstats.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- a/kernel/taskstats.c~taskstats-drop-the-unused-cpu_dont_care-enum-member
+++ a/kernel/taskstats.c
@@ -59,8 +59,7 @@ static DEFINE_PER_CPU(struct listener_li
enum actions {
REGISTER,
- DEREGISTER,
- CPU_DONT_CARE
+ DEREGISTER
};
static int prepare_reply(struct genl_info *info, u8 cmd, struct sk_buff **skbp,
_
Patches currently in -mm which might be from brads@mainlining.org are
watchdog-perf-one-digit-too-short-in-the-raw-event-config-copy.patch
reply other threads:[~2026-10-07 2:05 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=20261007020511.4C9301F0089C@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=balbirs@nvidia.com \
--cc=brads@mainlining.org \
--cc=mm-commits@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 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.