Linux Trace Kernel
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>, Yipeng Zou <zouyipeng@huawei.com>
Cc: shuah@kernel.org, mhiramat@kernel.org,
	linux-trace-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3] selftests/ftrace: traceonoff_triggers: strip off names
Date: Wed, 31 Dec 2025 12:50:10 -0700	[thread overview]
Message-ID: <382c86f1-03b0-40b7-aad6-143bdacd8a6f@linuxfoundation.org> (raw)
In-Reply-To: <20251218182719.34334341@gandalf.local.home>

On 12/18/25 16:27, Steven Rostedt wrote:
> On Sat, 13 Apr 2024 10:47:14 +0800
> Yipeng Zou <zouyipeng@huawei.com> wrote:
> 
>> 在 2023/8/21 23:13, Steven Rostedt 写道:
>>> On Fri, 18 Aug 2023 09:32:26 +0800
>>> Yipeng Zou <zouyipeng@huawei.com> wrote:
>>>   
>>>> The func_traceonoff_triggers.tc sometimes goes to fail
>>>> on my board, Kunpeng-920.
>>> Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
>>>
>>> Shuah, can you take this through your tree?
>>>
>>> -- Steve
>>
>> Hi:
>>
>>       I just notice that it haven't been picked in Linux-next.
>>
>>       It's there other issue about this patch?
> 
> Wow, this is a couple of years old (noticed while looking at the archived
> patches in patchwork).
> 
> Shuah, I believe this is still needed.
> 

Thanks for digging these up and others. It got buried deep
in my Inbox.

Applied to linux-kselftest fixes for the next rc

thanks,
-- Shuah


      reply	other threads:[~2025-12-31 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  1:32 [PATCH v3] selftests/ftrace: traceonoff_triggers: strip off names Yipeng Zou
2023-08-21 15:13 ` Steven Rostedt
2024-04-13  2:47   ` Yipeng Zou
2025-12-18 23:27     ` Steven Rostedt
2025-12-31 19:50       ` Shuah Khan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=382c86f1-03b0-40b7-aad6-143bdacd8a6f@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=zouyipeng@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox