[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190709114045.091c94f3@gandalf.local.home>
Date: Tue, 9 Jul 2019 11:40:45 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Mark Rutland <mark.rutland@....com>
Cc: Masami Hiramatsu <masami.hiramatsu@...il.com>,
Anders Roxell <anders.roxell@...aro.org>,
James Morse <james.morse@....com>,
"Naveen N . Rao" <naveen.n.rao@...ux.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
David Miller <davem@...emloft.net>,
Masami Hiramatsu <mhiramat@...nel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: kprobes sanity test fails on next-20190708
On Tue, 9 Jul 2019 16:37:55 +0100
Mark Rutland <mark.rutland@....com> wrote:
> > I agree. I pushed to my repo in the for-next branch. Care to test that?
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
>
> I've just given that a spin with KPROBES and KPROBES_SANITY_TEST
> selected, and it boots cleanly for me. FWIW:
>
> Tested-by: Mark Rutland <mark.rutland@....com>
Thanks, then I'm guessing no more changes need to be made.
I usually don't rebase my for-next branch for tags, but since I just
pushed it, I guess I can add this one ;-)
-- Steve
Powered by blists - more mailing lists