From: Shuah Khan <skhan@linuxfoundation.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <shuah@kernel.org>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3 4/7] selftests/ftrace: Convert required interface checks into requires list
Date: Fri, 19 Jun 2020 09:26:10 -0600 [thread overview]
Message-ID: <df1b214f-99d9-621c-0fb4-9b6a1d33eab8@linuxfoundation.org> (raw)
In-Reply-To: <20200617235822.76b94496733a3d7c5bb647b6@kernel.org>
On 6/17/20 8:58 AM, Masami Hiramatsu wrote:
> Hi Shuah,
>
> On Tue, 16 Jun 2020 10:48:12 -0600
> Shuah Khan <skhan@linuxfoundation.org> wrote:
>
>> On 6/11/20 6:03 AM, Shuah Khan wrote:
>>> On 6/10/20 7:32 AM, Steven Rostedt wrote:
>>>> On Wed, 10 Jun 2020 06:04:33 -0600
>>>> Shuah Khan <skhan@linuxfoundation.org> wrote:
>>>>
>>>>>> Steve, what would you think?
>>>>>
>>>>> No worries. As far as kselftest tree is concrned, I can apply these
>>>>> after rc1 comes out with Tom's patch.
>>>>>
>>>>> Or I can give Ack and Steve can take these through tracing tree.
>>>>
>>>> All my patches have already made it to Linus's tree. Perhaps
>>>> cherry-pick the commit needed from Linus's tree (it shouldn't break
>>>> anything when Linus pulls it). Just let Linus know what you did, and
>>>> everything should be fine.
>>>>
>>>
>>> Good to know. I will get these in.
>>>
>>
>> I applied all 7 patches to linux-kselftest next for my second update.
>> I saw a couple of merge problems with 4/7 patch even when I applied
>> it on top of with Tom's patch.
>
> Oh, I might miss something.
>
>>
>> I resolved them and amended the commit message to indicate the merge.
>> It is straight forward. Please check for sanity.
>
> Yes, I confirmed that the merge looks good, and also test ran out
> without any error. :)
>
Thanks for confirming. Pull request going out today.
thanks,
-- Shuah
next prev parent reply other threads:[~2020-06-19 15:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 2:40 [PATCH v3 0/7] selftsts/ftrace: Add requires list for each test case Masami Hiramatsu
2020-06-03 2:40 ` [PATCH v3 1/7] selftests/ftrace: Allow ":" in description Masami Hiramatsu
2020-06-03 2:40 ` [PATCH v3 2/7] selftests/ftrace: Return unsupported for the unconfigured features Masami Hiramatsu
2020-06-03 2:40 ` [PATCH v3 3/7] selftests/ftrace: Add "requires:" list support Masami Hiramatsu
2020-06-03 2:40 ` [PATCH v3 4/7] selftests/ftrace: Convert required interface checks into requires list Masami Hiramatsu
2020-06-09 20:41 ` Shuah Khan
2020-06-10 5:55 ` Masami Hiramatsu
2020-06-10 12:04 ` Shuah Khan
2020-06-10 13:32 ` Steven Rostedt
2020-06-11 12:03 ` Shuah Khan
2020-06-11 14:36 ` Masami Hiramatsu
2020-06-16 16:48 ` Shuah Khan
2020-06-17 14:58 ` Masami Hiramatsu
2020-06-19 15:26 ` Shuah Khan [this message]
2020-06-03 2:40 ` [PATCH v3 5/7] selftests/ftrace: Convert check_filter_file() with " Masami Hiramatsu
2020-06-03 2:40 ` [PATCH v3 6/7] selftests/ftrace: Support ":tracer" suffix for requires Masami Hiramatsu
2020-06-03 2:41 ` [PATCH v3 7/7] selftests/ftrace: Support ":README" " Masami Hiramatsu
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=df1b214f-99d9-621c-0fb4-9b6a1d33eab8@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tom.zanussi@linux.intel.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
all inboxes | Powered by JetHome®