public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Vasily Gorbik <gor@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Heiko Carstens <hca@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [GIT PULL] s390 updates for 6.0-rc5
Date: Sat, 10 Sep 2022 13:00:04 +0200	[thread overview]
Message-ID: <your-ad-here.call-01662807604-ext-8310@work.hours> (raw)

Hello Linus,

please pull s390 changes for 6.0-rc5.

Thank you,
Vasily

The following changes since commit 7c8d42fdf1a84b1a0dd60d6528309c8ec127e87c:

  s390/hugetlb: fix prepare_hugepage_range() check for 2 GB hugepages (2022-08-30 21:57:07 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-6.0-4

for you to fetch changes up to 8d96bba75a43ba564bf8732e955d9f519d2bbaec:

  s390/smp: enforce lowcore protection on CPU restart (2022-09-07 14:04:01 +0200)

----------------------------------------------------------------
s390 updates for 6.0-rc5

- Fix absolute zero lowcore corruption on kdump when CPU0 is offline.

- Fix lowcore protection setup for offline CPU restart.

----------------------------------------------------------------
Alexander Gordeev (2):
      s390/boot: fix absolute zero lowcore corruption on boot
      s390/smp: enforce lowcore protection on CPU restart

 arch/s390/kernel/nmi.c   | 2 +-
 arch/s390/kernel/setup.c | 3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)

             reply	other threads:[~2022-09-10 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-10 11:00 Vasily Gorbik [this message]
2022-09-10 17:38 ` [GIT PULL] s390 updates for 6.0-rc5 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=your-ad-here.call-01662807604-ext-8310@work.hours \
    --to=gor@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=hca@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