Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <4197d345-ff6f-ad43-bbfb-1f65635c191e@linuxfoundation.org>
Date:   Mon, 17 Oct 2022 08:32:05 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.2.2
Subject: Re: [PATCH] tracing: fix dynevent test requirements
To:     Steven Rostedt <rostedt@goodmis.org>,
        Mark Rutland <mark.rutland@arm.com>
Cc:     linux-kernel@vger.kernel.org, mhiramat@kernel.org,
        Shuah Khan <shuah@kernel.org>,
        Shuah Khan <skhan@linuxfoundation.org>
References: <20221017090741.2881918-1-mark.rutland@arm.com>
 <20221017103000.7d0fa449@gandalf.local.home>
Content-Language: en-US
From:   Shuah Khan <skhan@linuxfoundation.org>
In-Reply-To: <20221017103000.7d0fa449@gandalf.local.home>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 10/17/22 08:30, Steven Rostedt wrote:
> On Mon, 17 Oct 2022 10:07:41 +0100
> Mark Rutland <mark.rutland@arm.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