[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191220073240.GA72310@tuxmaker.boeblingen.de.ibm.com>
Date: Fri, 20 Dec 2019 08:32:40 +0100
From: Sven Schnelle <svens@...ux.ibm.com>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: Steven Rostedt <rostedt@...dmis.org>,
linux-trace-devel@...r.kernel.org,
Shuah Khan <shuahkhan@...il.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] selftests/ftrace: fix glob selftest
Hi,
On Fri, Dec 20, 2019 at 04:27:46PM +0900, Masami Hiramatsu wrote:
> On Thu, 19 Dec 2019 18:31:51 -0500
> Steven Rostedt <rostedt@...dmis.org> wrote:
>
> > On Wed, 18 Dec 2019 08:44:25 +0100
> > Sven Schnelle <svens@...ux.ibm.com> wrote:
> >
> > > test.d/ftrace/func-filter-glob.tc is failing on s390 because it has
> > > ARCH_INLINE_SPIN_LOCK and friends set to 'y'. So the usual
> > > __raw_spin_lock symbol isn't in the ftrace function list. Change
> > > '*aw*lock' to '*time*ns' which would hopefully match some of the
> > > ktime_() functions on all platforms.
> >
> > This requires an ack from Masami, and this patch can go through Shuah's
> > tree.
> >
> > Also, any patches for the Linux kernel should be Cc'd to lkml. The
> > linux-trace-devel is mostly for tracing tools, not kernel patches.
>
> Thanks Steve to CC to me.
> BTW, are there any reason why we use different symbols for different
> glob patterns?
> I mean we can use 'schedul*', '*chedule' and '*sch*ule' as test
> glob patterns.
Don't know, but i don't see a reason why we should have different patterns. If
there's an agreement that we prefer a common pattern i can update the patch and
resend.
Regards
Sven
Powered by blists - more mailing lists