From: Max Filippov <jcmvbkbc@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-xtensa@linux-xtensa.org,
Chris Zankel <chris@zankel.net>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: [PULL 0/7] xtensa updates for v5.2
Date: Fri, 10 May 2019 12:41:02 -0700 [thread overview]
Message-ID: <20190510194102.28038-1-jcmvbkbc@gmail.com> (raw)
Hi Linus,
please pull the following batch of updates for the Xtensa architecture:
The following changes since commit e93c9c99a629c61837d5a7fc2120cd2b6c70dbdd:
Linux 5.1 (2019-05-05 17:42:58 -0700)
are available in the git repository at:
git://github.com/jcmvbkbc/linux-xtensa.git tags/xtensa-20190510
for you to fetch changes up to a5944195d00a359e28d6e093593609bcee37ed5e:
xtensa: implement initialize_cacheattr for MPU cores (2019-05-07 10:36:34 -0700)
----------------------------------------------------------------
Xtensa updates for v5.2:
- implement atomic operations using exclusive access Xtensa option
operations.
- add support for Xtensa cores with memory protection unit (MPU).
- clean up xtensa-specific kernel-only headers.
- fix error path in simdisk_setup.
----------------------------------------------------------------
Chengguang Xu (2):
xtensa: fix incorrect fd close in error case of simdisk_setup()
xtensa: set proper error code for simdisk_setup()
Max Filippov (5):
xtensa: drop ifdef __KERNEL__ from kernel-only headers
xtensa: replace variant/core.h with asm/core.h
xtensa: clean up inline assembly in futex.h
xtensa: add exclusive atomics support
xtensa: implement initialize_cacheattr for MPU cores
arch/xtensa/Kconfig | 26 ++++-
arch/xtensa/boot/boot-redboot/bootstrap.S | 2 +-
arch/xtensa/include/asm/asmmacro.h | 2 +-
arch/xtensa/include/asm/atomic.h | 66 ++++++++++-
arch/xtensa/include/asm/barrier.h | 4 +
arch/xtensa/include/asm/bitops.h | 125 ++++++++++++++++++++-
arch/xtensa/include/asm/cache.h | 2 +-
arch/xtensa/include/asm/checksum.h | 2 +-
arch/xtensa/include/asm/cmpxchg.h | 36 +++++-
arch/xtensa/include/asm/coprocessor.h | 2 +-
arch/xtensa/include/asm/core.h | 21 ++++
arch/xtensa/include/asm/futex.h | 122 +++++++++++++-------
arch/xtensa/include/asm/initialize_mmu.h | 38 ++++++-
arch/xtensa/include/asm/io.h | 3 -
arch/xtensa/include/asm/irq.h | 2 +-
arch/xtensa/include/asm/pci-bridge.h | 3 -
arch/xtensa/include/asm/pci.h | 4 -
arch/xtensa/include/asm/pgalloc.h | 3 -
arch/xtensa/include/asm/processor.h | 2 +-
arch/xtensa/include/asm/ptrace.h | 2 +-
arch/xtensa/include/asm/vectors.h | 2 +-
arch/xtensa/kernel/hw_breakpoint.c | 2 +-
arch/xtensa/kernel/setup.c | 3 +
arch/xtensa/kernel/vmlinux.lds.S | 2 +-
arch/xtensa/lib/checksum.S | 2 +-
arch/xtensa/lib/memcopy.S | 2 +-
arch/xtensa/lib/memset.S | 2 +-
arch/xtensa/lib/strncpy_user.S | 2 +-
arch/xtensa/lib/strnlen_user.S | 2 +-
arch/xtensa/lib/usercopy.S | 2 +-
arch/xtensa/platforms/iss/simdisk.c | 3 +-
.../platforms/xt2000/include/platform/hardware.h | 2 +-
.../platforms/xt2000/include/platform/serial.h | 2 +-
33 files changed, 397 insertions(+), 98 deletions(-)
create mode 100644 arch/xtensa/include/asm/core.h
--
Thanks.
-- Max
next reply other threads:[~2019-05-10 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 19:41 Max Filippov [this message]
2019-05-11 15:00 ` 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=20190510194102.28038-1-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=chris@zankel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.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
all inboxes | Powered by JetHome®