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 updates for kernel v5.2
Date: Tue, 14 May 2019 22:00:10 +0200 [thread overview]
Message-ID: <20190514200010.GA30418@ls3530.dellerweb.de> (raw)
Hi Linus,
please pull two small additional enhancements for this merge window for the
parisc architecture for kernel 5.2 from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git parisc-5.2-2
Two small enhancements, which I didn't included in the last pull request
because I wanted to keep them a few more days in for-next before sending
upstream:
- Replace the ldcw barrier instruction by a nop instruction in the CAS code on
uniprocessor machines.
- Map variables read-only after init (enable ro_after_init feature).
Thanks,
Helge
----------------------------------------------------------------
Helge Deller (14):
parisc: Drop LDCW barrier in CAS code when running UP
parisc: Enable the ro_after_init feature
parisc: Use __ro_after_init in cache.c
parisc: Use __ro_after_init in drivers.c
parisc: Use __ro_after_init in firmware.c
parisc: Use __ro_after_init in head.S
parisc: Use __ro_after_init in inventory.c
parisc: Use __ro_after_init in pci.c
parisc: Use __ro_after_init in perf_images.h
parisc: Use __ro_after_init in process.c
parisc: Use __ro_after_init in processor.c
parisc: Use __ro_after_init in time.c
parisc: Use __ro_after_init in unwind.c
parisc: Use __ro_after_init in init.c
arch/parisc/include/asm/cache.h | 3 --
arch/parisc/kernel/cache.c | 16 ++++-----
arch/parisc/kernel/drivers.c | 2 +-
arch/parisc/kernel/firmware.c | 2 +-
arch/parisc/kernel/head.S | 2 +-
arch/parisc/kernel/inventory.c | 8 ++---
arch/parisc/kernel/pci.c | 8 ++---
arch/parisc/kernel/perf_images.h | 4 +--
arch/parisc/kernel/process.c | 2 +-
arch/parisc/kernel/processor.c | 4 +--
arch/parisc/kernel/syscall.S | 12 ++++---
arch/parisc/kernel/time.c | 2 +-
arch/parisc/kernel/unwind.c | 2 +-
arch/parisc/kernel/vmlinux.lds.S | 3 --
arch/parisc/mm/init.c | 75 +++++++++++++++++++++-------------------
15 files changed, 73 insertions(+), 72 deletions(-)
next reply other threads:[~2019-05-14 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 20:00 Helge Deller [this message]
2019-05-14 20:25 ` [GIT PULL] parisc architecture updates for kernel v5.2 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-05-07 18:38 Helge Deller
2019-05-08 2:40 ` 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=20190514200010.GA30418@ls3530.dellerweb.de \
--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).