[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170413055024.GA30806@naverao1-tp.localdomain>
Date: Thu, 13 Apr 2017 11:20:24 +0530
From: "Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: Michael Ellerman <mpe@...erman.id.au>,
Ananth N Mavinakayanahalli <ananth@...ux.vnet.ibm.com>,
Ingo Molnar <mingo@...nel.org>, linuxppc-dev@...ts.ozlabs.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/5] powerpc: a few kprobe fixes and refactoring
On 2017/04/13 12:02PM, Masami Hiramatsu wrote:
> Hi Naveen,
Hi Masami,
>
> BTW, I saw you sent 3 different series, are there any
> conflict each other? or can we pick those independently?
Yes, all these three patch series are based off powerpc/next and they do
depend on each other, as they are all about powerpc kprobes.
Patches 1 and 2 in this series touch generic kprobes bits and Michael
was planning on putting those in a topic branch so that -tip can pull
them too.
Apart from those two, your optprobes patch 3/5
(https://patchwork.ozlabs.org/patch/749934/) also touches generic code,
but it is needed for KPROBES_ON_FTRACE on powerpc. So, I've posted that
as part of my series. We could probably also put that in the topic
branch.
Thanks,
Naveen
Powered by blists - more mailing lists