mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: alistair@popple.id.au, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, mhiramat@kernel.org,
	naveen.n.rao@linux.vnet.ibm.com, npiggin@gmail.com,
	ravi.bangoria@linux.vnet.ibm.com, rostedt@goodmis.org
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-4.12-7 tag
Date: Sat, 24 Jun 2017 09:09:08 +1000	[thread overview]
Message-ID: <87injmpai3.fsf@concordia.ellerman.id.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 2244 bytes --]

Hi Linus,

Please pull some more powerpc fixes for 4.12. Most of these actually came in
last week but got held up for some more testing.

The following changes since commit a093c92dc7f96a15de98ec8cfe38e6f7610a5969:

  powerpc/debug: Add missing warn flag to WARN_ON's non-builtin path (2017-06-16 16:10:37 +1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-4.12-7

for you to fetch changes up to 34f19ff1b5a0d11e46df479623d6936460105c9f:

  powerpc/64: Initialise thread_info for emergency stacks (2017-06-23 13:25:38 +1000)

----------------------------------------------------------------
powerpc fixes for 4.12 #7

 - three fixes for kprobes/ftrace/livepatch interactions.

 - properly handle data breakpoints when using the Radix MMU.

 - fix for perf sampling of registers during call_usermodehelper().

 - properly initialise the thread_info on our emergency stacks.

 - add an explicit flush when doing TLB invalidations for a process
   using NPU2.

Thanks to:
  Alistair Popple, Naveen N. Rao, Nicholas Piggin, Ravi Bangoria,
  Masami Hiramatsu.

----------------------------------------------------------------
Alistair Popple (1):
      powerpc/powernv/npu-dma: Add explicit flush when sending an ATSD

Naveen N. Rao (4):
      powerpc/kprobes: Pause function_graph tracing during jprobes handling
      powerpc/ftrace: Pass the correct stack pointer for DYNAMIC_FTRACE_WITH_REGS
      powerpc/kprobes: Skip livepatch_handler() for jprobes
      powerpc/64s: Handle data breakpoints in Radix mode

Nicholas Piggin (1):
      powerpc/64: Initialise thread_info for emergency stacks

Ravi Bangoria (1):
      powerpc/perf: Fix oops when kthread execs user process

 arch/powerpc/include/asm/kprobes.h             |  1 +
 arch/powerpc/kernel/exceptions-64s.S           | 11 +--
 arch/powerpc/kernel/kprobes.c                  | 17 +++++
 arch/powerpc/kernel/setup_64.c                 | 31 ++++++++-
 arch/powerpc/kernel/trace/ftrace_64_mprofile.S | 59 ++++++++++++----
 arch/powerpc/perf/perf_regs.c                  |  3 +-
 arch/powerpc/platforms/powernv/npu-dma.c       | 94 ++++++++++++++++++--------
 7 files changed, 166 insertions(+), 50 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

                 reply	other threads:[~2017-06-23 23:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87injmpai3.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=alistair@popple.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mhiramat@kernel.org \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=ravi.bangoria@linux.vnet.ibm.com \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®