public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 10 Jun 2020 06:04:33 -0600	[thread overview]
Message-ID: <5a658ffa-348a-436d-fb74-e01f56541d6b@linuxfoundation.org> (raw)
In-Reply-To: <20200610145535.747d2765d60e6e3923441768@kernel.org>

On 6/9/20 11:55 PM, Masami Hiramatsu wrote:
> Hi Shuah,
> 
> On Tue, 9 Jun 2020 14:41:27 -0600
> Shuah Khan <skhan@linuxfoundation.org> wrote:
> 
>> On 6/2/20 8:40 PM, Masami Hiramatsu wrote:
>>> Convert the required tracefs interface checking code with
>>> requires: list.
>>>
>>> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
>>> Reviewed-by: Tom Zanussi <zanussi@kernel.org>
>>> ---
>>>     Changes in v2: Fix trigger-onchange-action-hist.tc requires list.
>>
>> Masami,
>>
>> This patch doesn't apply to linux-kselftest next
>>
>> Patches 1-3 applied fine and this one failed. For now I will
>> hold off on applying this series.
> 
> Yes, there is another patch posted by Tom with his ftrace enhancement
> in tracing-next. Thus I commented on 0/7 as below.
> 

Sorry I made a note of it when I first looked at the series and
missed that when I was applying patches.

> ----
> Since this series depends on following 2 commits,
> 
> commit 619ee76f5c9f ("selftests/ftrace: Return unsupported if no
>   error_log file") on Shuah's Kselftest tree
> commit bea24f766efc ("selftests/ftrace: Distinguish between hist
>   and synthetic event checks") on Steven's Tracing tree
> 
> This can be applied on the tree which merged both of them.
> ----
> 
> I'm not sure how do I handle it. It is OK just modifying this
> for linux-kselftest, but in that case we will need another
> patch after merged both.
> 
> IMHO, since the kselftest must run correctly on older kernel,
> (and ftracetest does) Tom's kselftest patch should be merged
> into linux-kselftest instead of tracing tree.
> 
> 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.


thanks,
-- Shuah


  reply	other threads:[~2020-06-10 12:04 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 [this message]
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
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=5a658ffa-348a-436d-fb74-e01f56541d6b@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