From: Shuah Khan <shuahkh@osg.samsung.com>
To: Steven Rostedt <rostedt@goodmis.org>, lyang0 <lei.yang@windriver.com>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Shuah Khan <shuah@kernel.org>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] selftests: ftrace: add more config fragments
Date: Fri, 3 Nov 2017 08:24:36 -0600 [thread overview]
Message-ID: <64b210b8-43cc-d758-08cb-680beddfb69a@osg.samsung.com> (raw)
In-Reply-To: <20171103091318.72d1018b@vmware.local.home>
On 11/03/2017 07:13 AM, Steven Rostedt wrote:
> On Fri, 3 Nov 2017 15:23:56 +0800
> lyang0 <lei.yang@windriver.com> wrote:
>
>
>>>> diff --git a/tools/testing/selftests/ftrace/config b/tools/testing/selftests/ftrace/config
>>>> index 8a1c9f9..b01924c 100644
>>>> --- a/tools/testing/selftests/ftrace/config
>>>> +++ b/tools/testing/selftests/ftrace/config
>>>> @@ -1,2 +1,6 @@
>>>> CONFIG_KPROBES=y
>>>> CONFIG_FTRACE=y
>>>> +CONFIG_FUNCTION_PROFILER=y
>>>> +CONFIG_TRACER_SNAPSHOT=y
>>>> +CONFIG_STACK_TRACER=y
>>>> +CONFIG_HIST_TRIGGERS=y
>>>>
>>> Hi Steve/Masami,
>>>
>>> Are you good with this change. Please give me an Ack.
>>
>> Hi,
>>
>> any comments ?
>
> You should have Cc'd me in the first email. Thanks to Shuah for
> pointing it out to us.
>
> Anyway, I'm fine with it.
>
> Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
>
Thanks Steve. I will get this into linux-kselftest 4.15-rc1
Lei,
Please do the following when you send your future patches:
Not stating the obvious, make sure to test and include what does
this patch fix in your commit log.
1. Run scripts/checkpatch.pl
2. Run scripts/get_maintainer.pl
3. Please give us at least a week before pinging us. We have all
been traveling all of last week and going through out Inboxes.
Please refer to Documentation/process/submitting-patches.rst
for details on how to send patches.
btw for this patch if you ran scripts/get_maintainer.pl, you would
have seen the correct list to send the patch to in the first place,
which would have made it easier.
Steven Rostedt <rostedt@goodmis.org> (maintainer:TRACING)
Ingo Molnar <mingo@redhat.com> (maintainer:TRACING)
Shuah Khan <shuah@kernel.org> (maintainer:KERNEL SELFTEST FRAMEWORK)
linux-kselftest@vger.kernel.org (open list:KERNEL SELFTEST FRAMEWORK)
linux-kernel@vger.kernel.org (open list)
thanks,
-- Shuah
prev parent reply other threads:[~2017-11-03 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 10:17 lei.yang
2017-11-01 22:06 ` Shuah Khan
2017-11-03 7:23 ` lyang0
2017-11-03 13:13 ` Steven Rostedt
2017-11-03 14:24 ` 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=64b210b8-43cc-d758-08cb-680beddfb69a@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=lei.yang@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
/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
all inboxes | Powered by JetHome®