linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	John David Anglin <dave.anglin@bell.net>
Subject: [GIT PULL] parisc architecture fixes for kernel v5.2-rc4
Date: Thu, 6 Jun 2019 17:40:15 +0200	[thread overview]
Message-ID: <20190606154015.GA13868@ls3530> (raw)

Hi Linus,

please pull some additional fixes and cleanups for the parisc architecture from:

  git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git parisc-5.2-3

Changes include
- Fix crashes when accessing PCI devices on some machines like C240 and J5000.
  The crashes were triggered because we replaced cache flushes by nops in the
  alternative coding where we shouldn't for some machines.
- Dave fixed a race in the usage of the sr1 space register when used to
  load the coherence index.
- Use the hardware lpa instruction to to load the physical address of kernel
  virtual addresses in the iommu driver code.
- The kernel may fail to link when CONFIG_MLONGCALLS isn't set. Solve that by
  rearranging functions in the final vmlinux executeable.
- Some defconfig cleanups and removal of compiler warnings.

Thanks,
Helge

----------------------------------------------------------------
Helge Deller (3):
      parisc: Allow building 64-bit kernel without -mlong-calls compiler option
      parisc: Fix compiler warnings in float emulation code
      parisc: Fix crash due alternative coding for NP iopdir_fdc bit

John David Anglin (2):
      parisc: Use implicit space register selection for loading the coherence index of I/O pdirs
      parisc: Use lpa instruction to load physical addresses in driver code

Krzysztof Kozlowski (1):
      parisc: configs: Remove useless UEVENT_HELPER_PATH

Mike Rapoport (1):
      parisc: Kconfig: remove ARCH_DISCARD_MEMBLOCK

Yury Norov (1):
      parisc/slab: cleanup after /proc/slab_allocators removal

 arch/parisc/Kconfig                         |  4 ++--
 arch/parisc/configs/712_defconfig           |  1 -
 arch/parisc/configs/a500_defconfig          |  1 -
 arch/parisc/configs/b180_defconfig          |  1 -
 arch/parisc/configs/c3000_defconfig         |  1 -
 arch/parisc/configs/c8000_defconfig         |  2 --
 arch/parisc/configs/default_defconfig       |  1 -
 arch/parisc/configs/generic-32bit_defconfig |  1 -
 arch/parisc/include/asm/special_insns.h     | 24 ++++++++++++++++++++++++
 arch/parisc/kernel/alternative.c            |  3 ++-
 arch/parisc/kernel/vmlinux.lds.S            | 21 ++++++++++++++-------
 arch/parisc/math-emu/cnv_float.h            |  8 ++++----
 drivers/parisc/ccio-dma.c                   |  6 ++----
 drivers/parisc/sba_iommu.c                  |  5 ++---
 14 files changed, 50 insertions(+), 29 deletions(-)

             reply	other threads:[~2019-06-06 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 15:40 Helge Deller [this message]
2019-06-06 20:20 ` [GIT PULL] parisc architecture fixes for kernel v5.2-rc4 pr-tracker-bot

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=20190606154015.GA13868@ls3530 \
    --to=deller@gmx.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dave.anglin@bell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).