From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: aneesh.kumar@linux.vnet.ibm.com, bsingharora@gmail.com,
fbarrat@linux.vnet.ibm.com, hkallweit1@gmail.com,
imunsie@au1.ibm.com, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, sfr@canb.auug.org.au,
vaibhav@linux.vnet.ibm.com
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-4.9-3 tag
Date: Sat, 22 Oct 2016 09:34:36 +1100 [thread overview]
Message-ID: <871sz9z5z7.fsf@concordia.ellerman.id.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2363 bytes --]
Hi Linus,
Please pull some more powerpc fixes for 4.9:
The following changes since commit 1001354ca34179f3db924eb66672442a173147dc:
Linux 4.9-rc1 (2016-10-15 12:17:50 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-4.9-3
for you to fetch changes up to 78914ff0843623ee6dbeae92fa0bb8761828684e:
powerpc: Ignore the pkey system calls for now (2016-10-19 20:36:24 +1100)
----------------------------------------------------------------
powerpc fixes for 4.9 #3
Fixes marked for stable:
- Prevent unlikely crash in copro_calculate_slb() (Frederic Barrat)
- cxl: Prevent adapter reset if an active context exists (Vaibhav Jain)
Fixes for code merged this cycle:
- Fix boot on systems with uncompressed kernel image (Heiner Kallweit)
- Drop dump_numa_memory_topology() (Michael Ellerman)
- Fix numa topology console print (Aneesh Kumar K.V)
- Ignore the pkey system calls for now (Stephen Rothwell)
----------------------------------------------------------------
Aneesh Kumar K.V (1):
powerpc: Fix numa topology console print
Frederic Barrat (1):
powerpc/mm: Prevent unlikely crash in copro_calculate_slb()
Heiner Kallweit (1):
powerpc/boot: Fix boot on systems with uncompressed kernel image
Michael Ellerman (1):
powerpc/mm: Drop dump_numa_memory_topology()
Stephen Rothwell (1):
powerpc: Ignore the pkey system calls for now
Vaibhav Jain (1):
cxl: Prevent adapter reset if an active context exists
Documentation/ABI/testing/sysfs-class-cxl | 7 +++--
arch/powerpc/boot/main.c | 18 ++++++++++--
arch/powerpc/include/asm/unistd.h | 4 +++
arch/powerpc/mm/copro_fault.c | 2 ++
arch/powerpc/mm/numa.c | 46 ++++---------------------------
drivers/misc/cxl/api.c | 9 ++++++
drivers/misc/cxl/context.c | 3 ++
drivers/misc/cxl/cxl.h | 24 ++++++++++++++++
drivers/misc/cxl/file.c | 11 ++++++++
drivers/misc/cxl/guest.c | 3 ++
drivers/misc/cxl/main.c | 42 +++++++++++++++++++++++++++-
drivers/misc/cxl/pci.c | 2 ++
drivers/misc/cxl/sysfs.c | 27 +++++++++++++++---
13 files changed, 148 insertions(+), 50 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
reply other threads:[~2016-10-21 22:34 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=871sz9z5z7.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bsingharora@gmail.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=hkallweit1@gmail.com \
--cc=imunsie@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=vaibhav@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;
as well as URLs for NNTP newsgroup(s).