mirror of https://lore.kernel.org/lkml/
 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 updates for kernel v4.19
Date: Mon, 13 Aug 2018 19:13:19 +0200	[thread overview]
Message-ID: <20180813171319.GA16531@ls3530.fritz.box> (raw)

Hi Linus,

please pull fixes and updates for the parisc architecture for kernel 4.19 from:

  git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git parisc-4.19-1

Changes include:
- parisc now uses the generic dma_noncoherent_ops implementation, by Christoph Hellwig.
- further memory barrier and spinlock improvements, by John David Anglin.
- prepare removal of current_text_addr() functions, by Nick Desaulniers.
- improve kernel stack unwinding on parisc, by me.
- drop ENOTSUP which was defined on parisc only, by me.

Thanks,
Helge

----------------------------------------------------------------
Christoph Hellwig (3):
      parisc: merge pcx_dma_ops and pcxl_dma_ops
      parisc: always use flush_kernel_dcache_range for DMA cache maintainance
      parisc: use generic dma_noncoherent_ops

Helge Deller (3):
      parisc: Drop architecture-specific ENOTSUP define
      parisc: Add HAVE_REGS_AND_STACK_ACCESS_API feature
      parisc: Fix and improve kernel stack unwinding

John David Anglin (2):
      parisc: Remove ordered stores from syscall.S
      parisc: Remove unnecessary barriers from spinlock.h

Nick Desaulniers (1):
      parisc: prefer _THIS_IP_ and _RET_IP_ statement expressions

 arch/parisc/Kconfig                        |   5 +
 arch/parisc/include/asm/assembly.h         |   2 +
 arch/parisc/include/asm/dma-mapping.h      |   5 -
 arch/parisc/include/asm/linkage.h          |  17 ++-
 arch/parisc/include/asm/ptrace.h           |  11 ++
 arch/parisc/include/asm/spinlock.h         |   8 +-
 arch/parisc/include/asm/unwind.h           |   3 +
 arch/parisc/include/uapi/asm/errno.h       |   1 -
 arch/parisc/kernel/entry.S                 |  53 +++-----
 arch/parisc/kernel/pacache.S               | 125 ------------------
 arch/parisc/kernel/pci-dma.c               | 199 +++++------------------------
 arch/parisc/kernel/process.c               |   2 +-
 arch/parisc/kernel/ptrace.c                | 100 +++++++++++++++
 arch/parisc/kernel/real2.S                 |   6 -
 arch/parisc/kernel/setup.c                 |   8 +-
 arch/parisc/kernel/syscall.S               |  24 ++--
 arch/parisc/kernel/traps.c                 |   2 +-
 arch/parisc/kernel/unwind.c                |  93 ++++++++------
 arch/parisc/lib/lusercopy.S                |  21 ---
 arch/parisc/mm/init.c                      |  11 +-
 kernel/time/posix-timers.c                 |  13 +-
 tools/arch/parisc/include/uapi/asm/errno.h |   1 -
 22 files changed, 262 insertions(+), 448 deletions(-)

                 reply	other threads:[~2018-08-13 17:13 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=20180813171319.GA16531@ls3530.fritz.box \
    --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

all inboxes | Powered by JetHome®