From: Steven Rostedt <rostedt@goodmis.org>
To: Valentin Schneider <vschneid@redhat.com>
Cc: John Stultz <jstultz@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
K Prateek Nayak <kprateek.nayak@amd.com>
Subject: Re: [PATCH] MAINTAINERS: Add K Prateek Nayak to scheduler reviewers
Date: Thu, 26 Mar 2026 10:54:30 -0400 [thread overview]
Message-ID: <20260326105430.3df5f679@gandalf.local.home> (raw)
In-Reply-To: <xhsmhecl6hpng.mognet@vschneid-thinkpadt14sgen2i.remote.csb>
On Thu, 26 Mar 2026 11:05:23 +0100
Valentin Schneider <vschneid@redhat.com> wrote:
> On 25/03/26 17:26, John Stultz wrote:
> > I've been fortunate to have K Prateek take an active interest in
> > my Proxy Execution patches. He's provided great review insights
> > and productive feedback, sometimes remembering the subtleties of
> > the patch series better than I do myself! And he has done all
> > this with great kindness and humility.
> >
> > I've really appreciated his reviews, and I think everyone should
> > be so lucky, so I wanted to propose adding him to the scheduler
> > reviewers list.
> >
> > Signed-off-by: John Stultz <jstultz@google.com>
>
> That doesn't need any more Acks, but I did want to add that his reviewing
> efforts have been helpful and are greatly appreciated :)
You can always add another ack, it just shows how acceptable the commit is ;-)
-- Steve
next prev parent reply other threads:[~2026-03-26 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 17:26 John Stultz
2026-03-25 17:48 ` Steven Rostedt
2026-03-26 4:13 ` K Prateek Nayak
2026-03-26 6:58 ` Juri Lelli
2026-03-26 7:31 ` Vincent Guittot
2026-03-26 8:43 ` Dietmar Eggemann
2026-03-26 10:05 ` Valentin Schneider
2026-03-26 14:54 ` Steven Rostedt [this message]
2026-03-26 11:48 ` [tip: sched/core] " tip-bot2 for John Stultz
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=20260326105430.3df5f679@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®