[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241122153259.4c1c9e38@gandalf.local.home>
Date: Fri, 22 Nov 2024 15:32:59 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org, Peter
Zijlstra <peterz@...radead.org>, tglx@...utronix.de, mingo@...nel.org,
juri.lelli@...hat.com, vincent.guittot@...aro.org,
dietmar.eggemann@....com, bsegall@...gle.com, mgorman@...e.de,
vschneid@...hat.com, ankur.a.arora@...cle.com, efault@....de, Masami
Hiramatsu <mhiramat@...nel.org>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>
Subject: Re: [PATCH v3] tracing: Record task flag NEED_RESCHED_LAZY.
On Fri, 22 Nov 2024 21:29:52 +0100
Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:
> On 2024-11-22 14:58:39 [-0500], Steven Rostedt wrote:
> > Actually, on Monday, can you send me a v4 with this fix?
>
> already done.
Thanks.
>
> > I just realized that this patch depends on both my branch (which I'm still
> > waiting for Linus to pull) and the code that is already in Linus's tree.
> > Once Linus pulls my branch, I'll apply this on that merge commit. But that
> > will not be until next week.
>
> okay. But that one is ready ;)
Yeah, but I can't do anything with it until Linus pulls in my branch. And I
did the pull request on Wednesday. Would have been earlier, but some people
sent me some bug fixes, so I decided to add them on top. But that required
the normal testing and pushing to linux-next, and waiting a few days.
-- Steve
Powered by blists - more mailing lists