From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: amodra@gmail.com, aneesh.kumar@linux.vnet.ibm.com,
chandan@linux.vnet.ibm.com, dan.j.williams@intel.com,
gwshan@linux.vnet.ibm.com, hegdevasant@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
maddy@linux.vnet.ibm.com, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-4.5-2 tag
Date: Fri, 29 Jan 2016 20:31:25 +1100 [thread overview]
Message-ID: <1454059885.7560.1.camel@ellerman.id.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2314 bytes --]
Hi Linus,
Please pull powerpc fixes for 4.5:
The following changes since commit 9fa686068a32ddf256df03982b3e3967c18654a8:
Merge tag 'dmaengine-fix-4.5-rc1' of git://git.infradead.org/users/vkoul/slave-dma (2016-01-20 10:15:21 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-4.5-2
for you to fetch changes up to 2d19fc639516dc7b4184450b315c931d38549e61:
powerpc/mm: Fixup _HPAGE_CHG_MASK (2016-01-28 23:49:43 +1100)
----------------------------------------------------------------
powerpc fixes for 4.5
- Wire up copy_file_range() syscall from Chandan Rajendra
- Simplify module TOC handling from Alan Modra
- Remove newly added extra definition of pmd_dirty from Stephen Rothwell
- Allow user space to map rtas_rmo_buf from Vasant Hegde
- Fix PE location code from Gavin Shan
- Remove PPMU_HAS_SSLOT flag for Power8 from Madhavan Srinivasan
- Fixup _HPAGE_CHG_MASK from Aneesh Kumar K.V
----------------------------------------------------------------
Alan Modra (1):
powerpc: Simplify module TOC handling
Aneesh Kumar K.V (1):
powerpc/mm: Fixup _HPAGE_CHG_MASK
Chandan Rajendra (1):
powerpc: Wire up copy_file_range() syscall
Gavin Shan (1):
powerpc/eeh: Fix PE location code
Madhavan Srinivasan (1):
powerpc/perf: Remove PPMU_HAS_SSLOT flag for Power8
Stephen Rothwell (1):
powerpc: Remove newly added extra definition of pmd_dirty
Vasant Hegde (1):
powerpc/mm: Allow user space to map rtas_rmo_buf
arch/powerpc/include/asm/book3s/64/hash.h | 4 +++-
arch/powerpc/include/asm/book3s/64/pgtable.h | 1 -
arch/powerpc/include/asm/systbl.h | 1 +
arch/powerpc/include/asm/unistd.h | 2 +-
arch/powerpc/include/uapi/asm/unistd.h | 1 +
arch/powerpc/kernel/eeh_pe.c | 33 +++++++++++++---------------
arch/powerpc/kernel/misc_64.S | 28 -----------------------
arch/powerpc/kernel/module_64.c | 12 +++++++---
arch/powerpc/mm/mem.c | 4 ++--
arch/powerpc/perf/power8-pmu.c | 2 +-
scripts/mod/modpost.c | 3 ++-
11 files changed, 35 insertions(+), 56 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2016-01-29 9:31 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=1454059885.7560.1.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=amodra@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=hegdevasant@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).