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/6] xtensa fixes for v5.4-rc4
Date: Thu, 17 Oct 2019 15:49:10 -0700 [thread overview]
Message-ID: <20191017224910.18457-1-jcmvbkbc@gmail.com> (raw)
Hi Linus,
please pull the following batch of fixes for the Xtensa architecture:
The following changes since commit 4f5cafb5cb8471e54afdc9054d973535614f7675:
Linux 5.4-rc3 (2019-10-13 16:37:36 -0700)
are available in the Git repository at:
git://github.com/jcmvbkbc/linux-xtensa.git tags/xtensa-20191017
for you to fetch changes up to 775fd6bfefc66a8c33e91dd9687ed530643b954d:
xtensa: fix change_bit in exclusive access option (2019-10-16 00:14:33 -0700)
----------------------------------------------------------------
Xtensa fixes for v5.4:
- fix {get,put}_user() for 64bit values;
- fix warning about static EXPORT_SYMBOL from modpost;
- fix PCI IO ports mapping for the virt board;
- fix pasto in change_bit for exclusive access option.
----------------------------------------------------------------
Al Viro (1):
xtensa: fix {get,put}_user() for 64bit values
Max Filippov (5):
xtensa: clean up assembly arguments in uaccess macros
xtensa: fix type conversion in __get_user_[no]check
xtensa: drop EXPORT_SYMBOL for outs*/ins*
xtensa: virt: fix PCI IO ports mapping
xtensa: fix change_bit in exclusive access option
arch/xtensa/boot/dts/virt.dts | 2 +-
arch/xtensa/include/asm/bitops.h | 2 +-
arch/xtensa/include/asm/uaccess.h | 94 ++++++++++++++++++++++-----------------
arch/xtensa/kernel/xtensa_ksyms.c | 7 ---
4 files changed, 55 insertions(+), 50 deletions(-)
--
Thanks.
-- Max
next reply other threads:[~2019-10-17 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 22:49 Max Filippov [this message]
2019-10-17 23:45 ` [PULL 0/6] xtensa fixes for v5.4-rc4 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=20191017224910.18457-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;
as well as URLs for NNTP newsgroup(s).