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>
Cc: Guenter Roeck <linux@roeck-us.net>
Subject: [GIT PULL] parisc architecture fixes for 4.14
Date: Thu, 19 Oct 2017 20:22:58 +0200 [thread overview]
Message-ID: <20171019182258.GA8290@ls3530.fritz.box> (raw)
Hi Linus,
please pull three small but important fixes for the parisc architecture for kernel 4.14 from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git parisc-4.14-3
Three small important fixes for the parisc architecture:
- Export __cmpxchg_u64() symbol on 32bit kernel too. This unbreaks building the
kernel with ixgbe kernel module. From Guenter Roeck.
- Fix 64-bit atomic cmpxchg kernel helper function for 32-bit kernel in LWS
code for userspace. This unbreaks e.g. the 64-bit variant of the glibc
function __sync_fetch_and_add() with a 32-bit parisc kernel. From John
David Anglin, tagged for backport to v3.13+.
- Detect nonsynchronous CPU-internal cr16 cycle counters more reliable. This
avoids stalled CPU warnings by the kernel soft lockup detector. From me,
tagged for backport to v4.13+.
Thanks,
Helge
----------------------------------------------------------------
Guenter Roeck (1):
parisc: Export __cmpxchg_u64 unconditionally
Helge Deller (1):
parisc: Fix detection of nonsynchronous cr16 cycle counters
John David Anglin (1):
parisc: Fix double-word compare and exchange in LWS code on 32-bit kernels
arch/parisc/kernel/parisc_ksyms.c | 2 +-
arch/parisc/kernel/syscall.S | 6 +++---
arch/parisc/kernel/time.c | 5 ++++-
3 files changed, 8 insertions(+), 5 deletions(-)
reply other threads:[~2017-10-19 18:23 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=20171019182258.GA8290@ls3530.fritz.box \
--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=linux@roeck-us.net \
--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
all inboxes | Powered by JetHome®