[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230620110227.6a944a19@gandalf.local.home>
Date: Tue, 20 Jun 2023 11:02:27 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Ajay Kaher <akaher@...are.com>
Cc: "mhiramat@...nel.org" <mhiramat@...nel.org>,
"shuah@...nel.org" <shuah@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-trace-kernel@...r.kernel.org"
<linux-trace-kernel@...r.kernel.org>,
"linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>,
Ching-lin Yu <chinglinyu@...gle.com>,
Nadav Amit <namit@...are.com>,
"srivatsa@...il.mit.edu" <srivatsa@...il.mit.edu>,
Alexey Makhalov <amakhalov@...are.com>,
Vasavi Sirnapalli <vsirnapalli@...are.com>,
Tapas Kundu <tkundu@...are.com>,
"er.ajay.kaher@...il.com" <er.ajay.kaher@...il.com>
Subject: Re: [PATCH v3 00/10] tracing: introducing eventfs
On Mon, 19 Jun 2023 05:38:25 +0000
Ajay Kaher <akaher@...are.com> wrote:
> # of passed: 65
> # of failed: 3
Unrelated to your patches, but have you checked why these fail? Do you have
the latest tests running on the latest kernel?
> # of unresolved: 6
> # of untested: 0
> # of unsupported: 44
> # of xfailed: 0
> # of undefined(test bug): 0
>
> These results are same with/without eventfs.
I'm hoping to look at these patches this week.
Thanks!
-- Steve
Powered by blists - more mailing lists