[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240716091851.GC26750@noisy.programming.kicks-ass.net>
Date: Tue, 16 Jul 2024 11:18:51 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Tio Zhang <tiozhang@...iglobal.com>, mhiramat@...nel.org,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
vineethr@...ux.ibm.com, akpm@...ux-foundation.org,
mathieu.desnoyers@...icios.com, mingo@...nel.org,
mgorman@...hsingularity.net, qyousef@...alina.io,
vincent.guittot@...aro.org, elver@...gle.com, zyhtheonly@...il.com,
zyhtheonly@...h.net, Juri Lelli <juri.lelli@...il.com>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Valentin Schneider <vschneid@...hat.com>
Subject: Re: [PATCH 1/1] tracing/sched: sched_switch: place prev_comm and
next_comm in right order
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@...iglobal.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.
Powered by blists - more mailing lists