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;
Date:   Mon, 17 Oct 2022 10:30:00 -0400
From:   Steven Rostedt <rostedt@goodmis.org>
To:     Mark Rutland <mark.rutland@arm.com>
Cc:     linux-kernel@vger.kernel.org, mhiramat@kernel.org,
        Shuah Khan <skhan@linuxfoundation.org>,
        Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] tracing: fix dynevent test requirements
Message-ID: <20221017103000.7d0fa449@gandalf.local.home>
In-Reply-To: <20221017090741.2881918-1-mark.rutland@arm.com>
References: <20221017090741.2881918-1-mark.rutland@arm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

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