[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <70b550a0-3d8a-528e-4e1f-10cfbaa874ef@roeck-us.net>
Date: Tue, 5 Apr 2022 20:49:10 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
f.fainelli@...il.com, sudipm.mukherjee@...il.com,
slade@...dewatkins.com
Subject: Re: [PATCH 5.10 000/599] 5.10.110-rc1 review
On 4/5/22 19:52, Steven Rostedt wrote:
> On Tue, 5 Apr 2022 19:30:25 -0700
> Guenter Roeck <linux@...ck-us.net> wrote:
>
>>> s390 tests crashed. Other failed qemu tests did not compile.
>>
>> Bisect points to commit 93fe2389e6fd ("tracing: Have TRACE_DEFINE_ENUM
>> affect trace event types as well"). Bisect log attached. Reverting the
>> offending patch fixes the problem. Copying Steven for comments/input.
>
> Do you have this commit?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=795301d3c2899
>
No, It applies, but doesn't compile.
kernel/trace/trace_events.c: In function 'update_event_fields':
kernel/trace/trace_events.c:2459:40: error: 'TRACE_EVENT_FL_DYNAMIC' undeclared
TRACE_EVENT_FL_DYNAMIC is not defined in v5.10.y.
Guenter
Powered by blists - more mailing lists