All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
	mhiramat@kernel.org, ananth@linux.vnet.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org, mingo@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [3/3] powerpc: kprobes: remove kprobe_exceptions_notify()
Date: Tue, 14 Feb 2017 23:40:26 +1100 (AEDT)	[thread overview]
Message-ID: <3vN27t2Sycz9s7t@ozlabs.org> (raw)
In-Reply-To: <4d802c747c86386fbf744021007b1cc74c8cdc59.1486496890.git.naveen.n.rao@linux.vnet.ibm.com>

On Tue, 2017-02-07 at 19:54:16 UTC, "Naveen N. Rao" wrote:
> ... as the weak variant will do.
> 
> Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/0ddde5004d26c483c9e67005b2be5b

cheers

WARNING: multiple messages have this Message-ID (diff)
From: patch-notifications@ellerman.id.au (Michael Ellerman)
To: linux-arm-kernel@lists.infradead.org
Subject: [3/3] powerpc: kprobes: remove kprobe_exceptions_notify()
Date: Tue, 14 Feb 2017 23:40:26 +1100 (AEDT)	[thread overview]
Message-ID: <3vN27t2Sycz9s7t@ozlabs.org> (raw)
In-Reply-To: <4d802c747c86386fbf744021007b1cc74c8cdc59.1486496890.git.naveen.n.rao@linux.vnet.ibm.com>

On Tue, 2017-02-07 at 19:54:16 UTC, "Naveen N. Rao" wrote:
> ... as the weak variant will do.
> 
> Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/0ddde5004d26c483c9e67005b2be5b

cheers

  reply	other threads:[~2017-02-14 12:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 19:54 [PATCH 1/3] kprobes: introduce weak variant of kprobe_exceptions_notify Naveen N. Rao
2017-02-07 19:54 ` Naveen N. Rao
2017-02-07 19:54 ` [PATCH 2/3] arm: kprobes: remove kprobe_exceptions_notify Naveen N. Rao
2017-02-07 19:54   ` Naveen N. Rao
2017-03-06 18:07   ` Naveen N. Rao
2017-03-06 18:07     ` Naveen N. Rao
2017-03-06 18:38     ` Russell King - ARM Linux
2017-03-06 18:38       ` Russell King - ARM Linux
2017-03-06 19:04       ` Naveen N. Rao
2017-03-06 19:04         ` Naveen N. Rao
2017-03-06 19:04         ` [PATCH 1/2] " Naveen N. Rao
2017-03-06 19:04           ` Naveen N. Rao
2017-03-06 19:04         ` [PATCH 2/2] arm64: " Naveen N. Rao
2017-03-06 19:04           ` Naveen N. Rao
2017-02-07 19:54 ` [PATCH 3/3] powerpc: kprobes: remove kprobe_exceptions_notify() Naveen N. Rao
2017-02-07 19:54   ` Naveen N. Rao
2017-02-14 12:40   ` Michael Ellerman [this message]
2017-02-14 12:40     ` [3/3] " Michael Ellerman
2017-02-08  1:45 ` [PATCH 1/3] kprobes: introduce weak variant of kprobe_exceptions_notify Masami Hiramatsu
2017-02-08  1:45   ` Masami Hiramatsu
2017-02-10  3:41 ` Michael Ellerman
2017-02-10  3:41   ` Michael Ellerman
2017-02-10  7:50   ` Ingo Molnar
2017-02-10  7:50     ` Ingo Molnar
2017-02-13  8:32   ` Naveen N. Rao
2017-02-13  8:32     ` Naveen N. Rao
2017-02-14 12:40 ` [1/3] " Michael Ellerman
2017-02-14 12:40   ` Michael Ellerman

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=3vN27t2Sycz9s7t@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.