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 v6.6-rc5
Date: Sat, 7 Oct 2023 20:53:15 +0200 [thread overview]
Message-ID: <ZSGpG0hwU9O5S9vD@p100> (raw)
Hi Linus,
please pull two parisc fixes kernel 6.6-rc5 which fix
* randome memory faults on pre-PA8800 CPUs, and
* boot issues.
Both patches are tagged for stable series.
They have been in for-next since kernel 6.6-rc2 without
any issues.
Thanks!
Helge
----------------------------------------------------------------
The following changes since commit ce9ecca0238b140b88f43859b211c9fdfd8e5b70:
Linux 6.6-rc2 (2023-09-17 14:40:24 -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.6-rc5
for you to fetch changes up to 914988e099fc658436fbd7b8f240160c352b6552:
parisc: Restore __ldcw_align for PA-RISC 2.0 processors (2023-10-07 20:30:16 +0200)
----------------------------------------------------------------
parisc architecture fixes for kernel v6.6-rc5:
* fix random faults in mmap'd memory on pre PA8800 processors
* fix boot crash with nr_cpus=1 on kernel command line
----------------------------------------------------------------
Helge Deller (1):
parisc: Fix crash with nr_cpus=1 option
John David Anglin (1):
parisc: Restore __ldcw_align for PA-RISC 2.0 processors
arch/parisc/include/asm/ldcw.h | 37 +++++++++++++++++---------------
arch/parisc/include/asm/spinlock_types.h | 5 -----
arch/parisc/kernel/smp.c | 4 +++-
3 files changed, 23 insertions(+), 23 deletions(-)
next reply other threads:[~2023-10-07 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 18:53 Helge Deller [this message]
2023-10-07 20:14 ` [GIT PULL] parisc architecture fixes for v6.6-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=ZSGpG0hwU9O5S9vD@p100 \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).