From: "tip-bot2 for Johannes Weiner" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Johannes Weiner <hannes@cmpxchg.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] MAINTAINERS: Add Peter explicitly to the psi section
Date: Wed, 09 Aug 2023 19:34:57 -0000 [thread overview]
Message-ID: <169160969747.27769.17107965601991518052.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20230801133235.GA1766885@cmpxchg.org>
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 113d0a6b3954b57907d1a6e3209f4174f504e0ae
Gitweb: https://git.kernel.org/tip/113d0a6b3954b57907d1a6e3209f4174f504e0ae
Author: Johannes Weiner <hannes@cmpxchg.org>
AuthorDate: Tue, 01 Aug 2023 09:18:21 -04:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Wed, 02 Aug 2023 16:19:25 +02:00
MAINTAINERS: Add Peter explicitly to the psi section
Peter is kind enough to route the low-volume psi patches through the
scheduler tree, but he is frequently not CC'd on them.
While he is matched through the SCHEDULER maintainers and reviewers on
kern/sched/*, that list is long, and mostly not applicable to psi
code. Thus, patch submitters often just CC the explicit PSI entries.
Add him to that section, to make sure he gets those patches.
Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20230801133235.GA1766885@cmpxchg.org
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index aee3406..f017dc6 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17047,6 +17047,7 @@ F: drivers/net/ppp/pptp.c
PRESSURE STALL INFORMATION (PSI)
M: Johannes Weiner <hannes@cmpxchg.org>
M: Suren Baghdasaryan <surenb@google.com>
+R: Peter Ziljstra <peterz@infradead.org>
S: Maintained
F: include/linux/psi*
F: kernel/sched/psi.c
prev parent reply other threads:[~2023-08-09 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 12:09 [PATCH] MAINTAINERS: add documentation to PSI section Ramazan Safiullin
2023-07-31 23:10 ` Suren Baghdasaryan
2023-07-31 23:12 ` Suren Baghdasaryan
2023-08-01 10:39 ` Peter Zijlstra
2023-08-01 11:07 ` Lukas Bulwahn
2023-08-01 13:03 ` Peter Zijlstra
2023-08-01 13:32 ` Johannes Weiner
2023-08-01 15:17 ` Peter Zijlstra
2023-08-09 19:34 ` tip-bot2 for Johannes Weiner [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=169160969747.27769.17107965601991518052.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@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
all inboxes | Powered by JetHome®