From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Tio Zhang <tiozhang@didiglobal.com>,
mhiramat@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, vineethr@linux.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
mingo@kernel.org, mgorman@techsingularity.net,
qyousef@layalina.io, vincent.guittot@linaro.org,
elver@google.com, zyhtheonly@gmail.com, zyhtheonly@yeah.net,
Juri Lelli <juri.lelli@gmail.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>
Subject: Re: [PATCH 1/1] tracing/sched: sched_switch: place prev_comm and next_comm in right order
Date: Tue, 16 Jul 2024 11:18:51 +0200 [thread overview]
Message-ID: <20240716091851.GC26750@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20240715150412.655abdda@rorschach.local.home>
On Mon, Jul 15, 2024 at 03:04:12PM -0400, Steven Rostedt wrote:
>
> [ Adding sched maintainers, as this is a scheduling trace event ]
>
> On Wed, 3 Jul 2024 11:33:53 +0800
> Tio Zhang <tiozhang@didiglobal.com> wrote:
>
> > Switch the order of prev_comm and next_comm in sched_switch's code to
> > align with its printing order.
>
> I'm going to pick this up in my tree, as it is pretty much a nop. It's
> just changing the ordering of the assignments of the comm names so that
> the copy of prev_comm is with the updates to the prev_fields, and the
> next_comm is with the updates to the next fields.
Right, have at. very close to a whitespace patch.
next prev parent reply other threads:[~2024-07-16 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 3:33 [PATCH 1/1] tracing/sched: sched_switch: place prev_comm and next_comm in right order Tio Zhang
2024-07-15 19:04 ` Steven Rostedt
2024-07-16 9:18 ` Peter Zijlstra [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-17 10:29 Tio Zhang
2024-04-23 10:24 ` Madadi Vineeth Reddy
2024-07-02 7:14 ` 张元瀚 Tio Zhang
2024-07-02 16:29 ` Steven Rostedt
2024-07-12 7:18 ` 张元瀚 Tio Zhang
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=20240716091851.GC26750@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=elver@google.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mgorman@techsingularity.net \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=qyousef@layalina.io \
--cc=rostedt@goodmis.org \
--cc=tiozhang@didiglobal.com \
--cc=vincent.guittot@linaro.org \
--cc=vineethr@linux.ibm.com \
--cc=vschneid@redhat.com \
--cc=zyhtheonly@gmail.com \
--cc=zyhtheonly@yeah.net \
/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