From: Steven Rostedt <rostedt@goodmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@redhat.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Clark Williams <williams@redhat.com>,
"Luis Claudio R. Goncalves" <lclaudio@uudg.org>,
John Kacur <jkacur@redhat.com>
Subject: Re: [PATCH] tracing: Update MAINTAINERS file
Date: Mon, 15 Jul 2024 15:13:37 -0400 [thread overview]
Message-ID: <20240715151337.2d47d003@rorschach.local.home> (raw)
In-Reply-To: <11fe922b-ffd4-4173-b1ff-d49745431fb0@efficios.com>
On Mon, 15 Jul 2024 15:10:17 -0400
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> On 2024-07-15 14:47, Steven Rostedt wrote:
> > From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
> >
> > Gone but never forgotten.
> >
> > [ Also moved Daniel's name to be consistent with the alphabetical order ]
>
> Hi Steven,
>
> You appear to have missed this entry from SCHEDULER:
>
> R: Daniel Bristot de Oliveira <bristot@redhat.com> (SCHED_DEADLINE)
>
> Should it be done in a separate commit or folded in this one ?
That has already been done:
https://lore.kernel.org/all/20240708075752.GF11386@noisy.programming.kicks-ass.net/
This patch is actually on top of that one.
-- Steve
next prev parent reply other threads:[~2024-07-15 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 18:47 [PATCH] tracing: Update MAINTAINERS file Steven Rostedt
2024-07-15 19:10 ` Mathieu Desnoyers
2024-07-15 19:13 ` Steven Rostedt [this message]
2024-07-15 19:16 ` Mathieu Desnoyers
2024-07-16 9:15 ` Masami Hiramatsu
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=20240715151337.2d47d003@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=jkacur@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=kstewart@linuxfoundation.org \
--cc=lclaudio@uudg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=williams@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