From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Steven Rostedt <rostedt@goodmis.org>
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:16:50 -0400 [thread overview]
Message-ID: <1c4375a2-f383-446e-9a21-edd768ded659@efficios.com> (raw)
In-Reply-To: <20240715151337.2d47d003@rorschach.local.home>
On 2024-07-15 15:13, Steven Rostedt wrote:
> 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.
Sorry I missed that.
Reviewed-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>
> -- Steve
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2024-07-15 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 18:47 Steven Rostedt
2024-07-15 19:10 ` Mathieu Desnoyers
2024-07-15 19:13 ` Steven Rostedt
2024-07-15 19:16 ` Mathieu Desnoyers [this message]
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=1c4375a2-f383-446e-9a21-edd768ded659@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--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=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®