[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4197d345-ff6f-ad43-bbfb-1f65635c191e@linuxfoundation.org>
Date: Mon, 17 Oct 2022 08:32:05 -0600
From: Shuah Khan <skhan@...uxfoundation.org>
To: Steven Rostedt <rostedt@...dmis.org>,
Mark Rutland <mark.rutland@....com>
Cc: linux-kernel@...r.kernel.org, mhiramat@...nel.org,
Shuah Khan <shuah@...nel.org>,
Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH] tracing: fix dynevent test requirements
On 10/17/22 08:30, Steven Rostedt wrote:
> On Mon, 17 Oct 2022 10:07:41 +0100
> Mark Rutland <mark.rutland@....com> wrote:
>
>> Currently a couple of dynevent tests will always report UNSUPPORTED and
>> not run, even when support is actually present.
>>
>> In commit:
>>
>> 95c104c378dc7d4c ("tracing: Auto generate event name when creating a group of events")
>>
>> The README text for synthetic events was changed from:
>>
>> "e[:[<group>/]<event>] <attached-group>.<attached-event> [<args>]\n"
>>
>> To:
>
> This was already fixed here:
>
> https://lore.kernel.org/all/20221010074207.714077-1-svens@linux.ibm.com/
>
> Shuah, can you take Sven's patch through your tree?
>
> Thanks,
>
> -- Steve
>
Yes. I will take this in for the next rc
thanks,
-- Shuah
Powered by blists - more mailing lists