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
Date: Wed, 8 Aug 2018 22:51:10 +0200 [thread overview]
Message-ID: <20180808205110.GA3398@ls3530> (raw)
Hi Linus,
would you please pull two important patches for the parisc architecture for kernel 4.18 from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git parisc-4.18-2
The first patch is trivial and fixes the kernel build if someone chooses to
build the generic 64bit defconfig. Alex Ghiti ran into that issue when he tried
to build a 4.18 kernel with his hugetlb patches on parisc64.
The patch from Dave adds missing memory barriers to the assembler unlock
sequences. Our hope is, that this should help us to fix the issues we rarely
still see with spinlocks.
Both patches had been in the for-next branch for a few days without any
reported issues and are tagged to be backported to all kernels above v4.0.
Thanks,
Helge
----------------------------------------------------------------
Helge Deller (1):
parisc: Enable CONFIG_MLONGCALLS by default
John David Anglin (1):
parisc: Define mb() and add memory barriers to assembler unlock sequences
arch/parisc/Kconfig | 2 +-
arch/parisc/include/asm/barrier.h | 32 ++++++++++++++++++++++++++++++++
arch/parisc/kernel/entry.S | 2 ++
arch/parisc/kernel/pacache.S | 1 +
arch/parisc/kernel/syscall.S | 4 ++++
5 files changed, 40 insertions(+), 1 deletion(-)
create mode 100644 arch/parisc/include/asm/barrier.h
reply other threads:[~2018-08-08 20:51 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=20180808205110.GA3398@ls3530 \
--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 NNTP newsgroup(s).