From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Anders Roxell <anders.roxell@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
James Morse <james.morse@arm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
"Naveen N . Rao" <naveen.n.rao@linux.ibm.com>,
David Miller <davem@davemloft.net>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: kprobes sanity test fails on next-20190708
Date: Wed, 10 Jul 2019 11:46:04 +0900 [thread overview]
Message-ID: <20190710114604.8e753774a93ece9d3e753646@kernel.org> (raw)
In-Reply-To: <20190709114045.091c94f3@gandalf.local.home>
On Tue, 9 Jul 2019 11:40:45 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Tue, 9 Jul 2019 16:37:55 +0100
> Mark Rutland <mark.rutland@arm.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@arm.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 ;-)
Thanks Steve!
--
Masami Hiramatsu <mhiramat@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-07-10 2:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 14:11 kprobes sanity test fails on next-20190708 Anders Roxell
2019-07-08 15:56 ` James Morse
2019-07-09 10:19 ` Anders Roxell
2019-07-09 12:36 ` Masami Hiramatsu
2019-07-09 15:25 ` Steven Rostedt
2019-07-09 15:37 ` Mark Rutland
2019-07-09 15:40 ` Steven Rostedt
2019-07-10 2:46 ` Masami Hiramatsu [this message]
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=20190710114604.8e753774a93ece9d3e753646@kernel.org \
--to=mhiramat@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=rostedt@goodmis.org \
/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;
as well as URLs for NNTP newsgroup(s).