LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: alastair@d-silva.org, andrew.donnellan@au1.ibm.com,
	bharata@linux.vnet.ibm.com, fbarrat@linux.vnet.ibm.com,
	linux-kernel@vger.kernel.org, linux@roeck-us.net,
	linuxppc-dev@lists.ozlabs.org
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-4.16-5 tag
Date: Fri, 09 Mar 2018 21:54:27 +1100	[thread overview]
Message-ID: <87fu59v7rw.fsf@concordia.ellerman.id.au> (raw)

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

Hi Linus,

Please pull some more powerpc fixes for 4.16:

The following changes since commit eb0a2d2620ae431c543963c8c7f08f597366fc60:

  powerpc/powernv: Support firmware disable of RFI flush (2018-02-23 16:55:42 +1100)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-4.16-5

for you to fetch changes up to b0c41b8b6e43120d7c35e4709508a3d90a09646e:

  powerpc/pseries: Fix vector5 in ibm architecture vector table (2018-03-06 23:05:38 +1100)

----------------------------------------------------------------
powerpc fixes for 4.16 #5

One notable fix to properly advertise our support for a new firmware feature,
caused by two series conflicting semantically but not textually.

There's a new ioctl for the new ocxl driver, which is not a fix, but needed to
complete the userspace API and good to have before the driver is in a released
kernel.

Finally three minor selftest fixes, and a fix for intermittent build failures
for some obscure platforms, caused by a missing make dependency.

Thanks to:
  Alastair D'Silva, Bharata B Rao, Guenter Roeck.

----------------------------------------------------------------
Alastair D'Silva (2):
      ocxl: Add get_metadata IOCTL to share OCXL information to userspace
      ocxl: Document the OCXL_IOCTL_GET_METADATA IOCTL

Bharata B Rao (1):
      powerpc/pseries: Fix vector5 in ibm architecture vector table

Guenter Roeck (1):
      powerpc/boot: Fix random libfdt related build errors

Michael Ellerman (3):
      selftests/powerpc: Skip tm-trap if transactional memory is not enabled
      selftests/powerpc: Fix missing clean of pmu/lib.o
      selftests/powerpc: Skip the subpage_prot tests if the syscall is unavailable

 Documentation/accelerators/ocxl.rst               |  5 +++++
 arch/powerpc/boot/Makefile                        |  3 ++-
 arch/powerpc/kernel/prom_init.c                   |  1 -
 drivers/misc/ocxl/file.c                          | 27 +++++++++++++++++++++++
 include/uapi/misc/ocxl.h                          | 17 ++++++++++++++
 tools/testing/selftests/powerpc/mm/subpage_prot.c | 14 ++++++++++++
 tools/testing/selftests/powerpc/tm/Makefile       |  2 +-
 tools/testing/selftests/powerpc/tm/tm-trap.c      |  2 ++
 8 files changed, 68 insertions(+), 3 deletions(-)

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

                 reply	other threads:[~2018-03-09 10:54 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=87fu59v7rw.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=alastair@d-silva.org \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=fbarrat@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=linuxppc-dev@lists.ozlabs.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