public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@kernel.org>
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 and updates for v6.18-rc1
Date: Fri, 10 Oct 2025 15:03:52 +0200	[thread overview]
Message-ID: <aOkEOBbCvAdGdF5c@p100> (raw)

Hi Linus,

Please pull the patches for the parisc architecture for this merge window.

Just some minor fixes & initial work on perf_events support.

Thanks!
Helge

-----------------------------

The following changes since commit e5f0a698b34ed76002dc5cff3804a61c80233a7a:

  Linux 6.17 (2025-09-28 14:39:22 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git tags/parisc-for-6.18-rc1

for you to fetch changes up to f4edb5c52c93b1bc676064472fb517566a3e2129:

  parisc: Fix iodc and device path return values on old machines (2025-10-09 23:45:04 +0200)

----------------------------------------------------------------
parisc architecture updates for kernel v6.18-rc1:

Minor enhancements and fixes, specifically:
- report emulation and alignment faults via perf
- add initial kernel-side support for perf_events
- small initialization fixes in the parisc firmware layer
- adjust TC* constants and avoid referencing termio structs to avoid
  userspace build errors.

----------------------------------------------------------------
Helge Deller (5):
      parisc: Report emulation faults via perf
      parisc: Report software alignment faults via perf
      parisc: Add initial kernel-side perf_event support
      parisc: Firmware: Fix returned path for PDC_MODULE_FIND on older machines
      parisc: Fix iodc and device path return values on old machines

John David Anglin (1):
      parisc: Remove spurious if statement from raw_copy_from_user()

Sam James (1):
      parisc: don't reference obsolete termio struct for TC* constants

 arch/parisc/Kconfig                      |  3 ++
 arch/parisc/include/asm/perf_event.h     |  8 +++-
 arch/parisc/include/uapi/asm/ioctls.h    |  8 ++--
 arch/parisc/include/uapi/asm/perf_regs.h | 63 ++++++++++++++++++++++++++++++++
 arch/parisc/kernel/Makefile              |  1 +
 arch/parisc/kernel/drivers.c             |  6 +++
 arch/parisc/kernel/firmware.c            |  3 +-
 arch/parisc/kernel/perf_event.c          | 27 ++++++++++++++
 arch/parisc/kernel/perf_regs.c           | 61 +++++++++++++++++++++++++++++++
 arch/parisc/kernel/traps.c               |  2 +
 arch/parisc/kernel/unaligned.c           |  2 +
 arch/parisc/lib/memcpy.c                 |  1 -
 12 files changed, 178 insertions(+), 7 deletions(-)
 create mode 100644 arch/parisc/include/uapi/asm/perf_regs.h
 create mode 100644 arch/parisc/kernel/perf_event.c
 create mode 100644 arch/parisc/kernel/perf_regs.c

             reply	other threads:[~2025-10-10 13:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-10 13:03 Helge Deller [this message]
2025-10-10 18:25 ` [GIT PULL] parisc architecture fixes and updates for v6.18-rc1 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=aOkEOBbCvAdGdF5c@p100 \
    --to=deller@kernel.org \
    --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