mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
	mhiramat@kernel.org, ananth@linux.vnet.ibm.com
Cc: mingo@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/3] kprobes: introduce weak variant of kprobe_exceptions_notify
Date: Fri, 10 Feb 2017 14:41:37 +1100	[thread overview]
Message-ID: <87vasizp8u.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <b0894e503195b13a5ed6319e897e673f376a748d.1486496890.git.naveen.n.rao@linux.vnet.ibm.com>

"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> writes:

> kprobe_exceptions_notify() is not used on some of the architectures such
> as arm[64] and powerpc anymore. Introduce a weak variant for such
> architectures.

I'll merge patch 1 & 3 via the powerpc tree for v4.11.

You can then send patch 2 to the arm guys after -rc1, or for 4.12.

cheers

  parent reply	other threads:[~2017-02-10  3:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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-03-06 18:07   ` Naveen N. Rao
2017-03-06 18:38     ` Russell King - ARM Linux
2017-03-06 19:04       ` Naveen N. Rao
2017-03-06 19:04       ` [PATCH 1/2] " Naveen N. Rao
2017-03-06 19:04       ` [PATCH 2/2] arm64: " Naveen N. Rao
2017-02-07 19:54 ` [PATCH 3/3] powerpc: kprobes: remove kprobe_exceptions_notify() Naveen N. Rao
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-10  3:41 ` Michael Ellerman [this message]
2017-02-10  7:50   ` Ingo Molnar
2017-02-13  8:32   ` Naveen N. Rao
2017-02-14 12:40 ` [1/3] " 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=87vasizp8u.fsf@concordia.ellerman.id.au \
    --to=mpe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®