public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [GIT PULL] more s390 updates for 6.19 merge window
Date: Wed, 10 Dec 2025 12:48:16 +0100	[thread overview]
Message-ID: <20251210114816.40732Adf-hca@linux.ibm.com> (raw)

Hi Linus,

please pull a couple of additional s390 updates for the 6.19 merge window.

Thanks,
Heiko

The following changes since commit 51d90a15fedf8366cb96ef68d0ea2d0bf15417d2:

  Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm (2025-12-05 17:01:20 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-6.19-2

for you to fetch changes up to 70075e3d0ca0b72cc983d03f7cd9796e43492980:

  s390/bug: Add missing alignment (2025-12-08 15:42:41 +0100)

----------------------------------------------------------------
more s390 updates for 6.19 merge window

- Use the MSI parent domain API instead of the legacy API for setup and
  teardown of PCI MSI IRQs

- Select POSIX_CPU_TIMERS_TASK_WORK now that VIRT_XFER_TO_GUEST_WORK has
  been implemented for s390

- Fix a KVM bug which can lead to guest memory corruption

- Fix KASAN shadow memory mapping for hotplugged memory

- Minor bug fixes and improvements

----------------------------------------------------------------
Claudio Imbrenda (1):
      KVM: s390: Fix gmap_helper_zap_one_page() again

Heiko Carstens (4):
      s390/vmur: Use scnprintf() instead of sprintf()
      s390: Select POSIX_CPU_TIMERS_TASK_WORK
      s390/bug: Add missing CONFIG_BUG ifdef again
      s390/bug: Add missing alignment

Tobias Schumacher (2):
      genirq: Change hwirq parameter to irq_hw_number_t
      s390/pci: Migrate s390 IRQ logic to IRQ domain API

Vasily Gorbik (3):
      s390/boot: Use entire page for PTEs
      s390/vmem: Support 2G page splitting for KASAN shadow freeing
      s390: Unmap early KASAN shadow on memory offlining

 arch/s390/Kconfig            |   2 +
 arch/s390/boot/vmem.c        |  16 +-
 arch/s390/include/asm/bug.h  |   5 +
 arch/s390/include/asm/page.h |   2 +
 arch/s390/include/asm/pci.h  |   5 +
 arch/s390/mm/gmap_helpers.c  |   9 +-
 arch/s390/mm/pageattr.c      |   2 +-
 arch/s390/mm/vmem.c          |  14 +-
 arch/s390/pci/pci.c          |   6 +
 arch/s390/pci/pci_bus.c      |  18 +-
 arch/s390/pci/pci_irq.c      | 392 +++++++++++++++++++++++++++----------------
 drivers/s390/char/sclp_mem.c |  16 ++
 drivers/s390/char/vmur.c     |   8 +-
 include/linux/irqdesc.h      |   6 +-
 kernel/irq/irqdesc.c         |   6 +-
 15 files changed, 333 insertions(+), 174 deletions(-)

             reply	other threads:[~2025-12-10 11:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-10 11:48 Heiko Carstens [this message]
2025-12-10 23:51 ` [GIT PULL] more s390 updates for 6.19 merge window 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=20251210114816.40732Adf-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@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