linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>, shuah@kernel.org
Cc: Xiao Yang <yangx.jy@cn.fujitsu.com>,
	mingo@redhat.com, ice_yangxiao@163.com,
	linux-kselftest@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests/ftrace: Add CONFIG_SAMPLE_FTRACE_DIRECT=m kconfig
Date: Thu, 30 Apr 2020 11:05:11 -0600	[thread overview]
Message-ID: <2bfe3ebd-eaed-4e6e-db4d-5670cb2066dc@linuxfoundation.org> (raw)
In-Reply-To: <34600011-aca9-76ec-fb04-1ddd55d1da91@linuxfoundation.org>

Hi Xiao Yang,

On 4/6/20 8:52 AM, Shuah Khan wrote:
> On 4/6/20 7:23 AM, Steven Rostedt wrote:
>> On Sun, 5 Apr 2020 09:44:57 +0800
>> Xiao Yang <yangx.jy@cn.fujitsu.com> wrote:
>>
>>> ftrace-direct.tc and kprobe-direct.tc require 
>>> CONFIG_SAMPLE_FTRACE_DIRECT=m
>>> so add it to config file which is used by merge_config.sh.
>>
>>
>> Shuah,
>>
>> Care to take this in your tree?
>>
>> Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
>>
> 

I took this patch and sending it in my pull request. Please
make sure your commit logs don't wrap in your future patches.
It makes it easier to read commit logs.

"Without CONFIG_DYNAMIC_FTRACE, some tests get failure because required
     filter 
files(set_ftrace_filter/available_filter_functions/stack_trace_filter)
     are missing.  So implement check_filter_file() and make all related 
tests
     check required filter files by it.

     BTW: set_ftrace_filter and available_filter_functions are 
introduced together
     so just check either of them."


thanks,
-- Shuah

      reply	other threads:[~2020-04-30 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05  1:44 [PATCH] selftests/ftrace: Add CONFIG_SAMPLE_FTRACE_DIRECT=m kconfig Xiao Yang
2020-04-06 13:23 ` Steven Rostedt
2020-04-06 14:52   ` Shuah Khan
2020-04-30 17:05     ` 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=2bfe3ebd-eaed-4e6e-db4d-5670cb2066dc@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=ice_yangxiao@163.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=yangx.jy@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).