From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: nacc@linux.vnet.ibm.com,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
jk@ozlabs.org, imunsie@au1.ibm.com, bobby.prani@gmail.com,
ddstreet@ieee.org, aneesh.kumar@linux.vnet.ibm.com
Subject: [git pull] Please pull mpe.git for-linus branch (for powerpc)
Date: Wed, 29 Oct 2014 19:52:19 +1100 [thread overview]
Message-ID: <1414572739.5922.4.camel@concordia> (raw)
[-- Attachment #1: Type: text/plain, Size: 2399 bytes --]
Hi Linus,
Here are some updates for powerpc.
There's some bug fixes or cleanups to facilitate fixes, a MAINTAINERS update,
and a new syscall (bpf).
cheers
The following changes since commit c3351dfabf5c78fb5ddc79d0f7b65ebd9e441337:
Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending (2014-10-21 13:06:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux.git for-linus
for you to fetch changes up to 2c0a33f9861d38631245f7ef434ecad3413324fb:
powerpc/numa: ensure per-cpu NUMA mappings are correct on topology update (2014-10-29 09:41:22 +1100)
----------------------------------------------------------------
Aneesh Kumar K.V (2):
powerpc/mm: Fix build error with hugetlfs disabled
powerpc/mm: Remove redundant #if case
Dan Streetman (1):
MAINTAINERS: nx-842 driver maintainer change
Ian Munsie (4):
cxl: Disable secondary hash in segment table
cxl: Refactor cxl_load_segment() and find_free_sste()
powerpc/mm: Use appropriate ESID mask in copro_calculate_slb()
cxl: Fix PSL error due to duplicate segment table entries
Jeremy Kerr (1):
powernv: Use _GLOBAL_TOC for opal wrappers
Michael Ellerman (1):
Revert "powerpc/powernv: Fix endian bug in LPC bus debugfs accessors"
Nishanth Aravamudan (2):
powerpc/numa: use cached value of update->cpu in update_cpu_topology
powerpc/numa: ensure per-cpu NUMA mappings are correct on topology update
Pranith Kumar (1):
powerpc: Wire up sys_bpf() syscall
MAINTAINERS | 2 +-
arch/powerpc/include/asm/hugetlb.h | 2 +-
arch/powerpc/include/asm/systbl.h | 1 +
arch/powerpc/include/asm/unistd.h | 2 +-
arch/powerpc/include/uapi/asm/unistd.h | 1 +
arch/powerpc/mm/copro_fault.c | 3 +-
arch/powerpc/mm/numa.c | 7 ++-
arch/powerpc/mm/slice.c | 3 +-
arch/powerpc/platforms/powernv/opal-lpc.c | 4 +-
arch/powerpc/platforms/powernv/opal-wrappers.S | 2 +-
drivers/misc/cxl/fault.c | 74 ++++++++++++++------------
drivers/misc/cxl/native.c | 4 +-
12 files changed, 56 insertions(+), 49 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-10-29 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 8:52 Michael Ellerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-27 5:53 [git pull] Please pull mpe.git for-linus branch (for powerpc) Michael Ellerman
2014-11-19 5:21 Michael Ellerman
2014-11-04 4:40 Michael Ellerman
2014-10-20 9:15 Michael Ellerman
2014-10-16 6:13 Michael Ellerman
2014-10-10 22:46 Michael Ellerman
2014-09-11 4:42 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=1414572739.5922.4.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bobby.prani@gmail.com \
--cc=ddstreet@ieee.org \
--cc=imunsie@au1.ibm.com \
--cc=jk@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nacc@linux.vnet.ibm.com \
--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