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/3] Xtensa fixes for v4.20-rc5
Date: Wed, 28 Nov 2018 12:07:16 -0800 [thread overview]
Message-ID: <20181128200716.29346-1-jcmvbkbc@gmail.com> (raw)
Hi Linus,
please pull the following batch of fixes for coprocessors on Xtensa
architecture.
The following changes since commit 2e6e902d185027f8e3cb8b7305238f7e35d6a436:
Linux 4.20-rc4 (2018-11-25 14:19:31 -0800)
are available in the git repository at:
git://github.com/jcmvbkbc/linux-xtensa.git tags/xtensa-20181128
for you to fetch changes up to 38a35a78c5e270cbe53c4fef6b0d3c2da90dd849:
xtensa: fix coprocessor part of ptrace_{get,set}xregs (2018-11-26 18:37:51 -0800)
----------------------------------------------------------------
Xtensa fixes for v4.20-rc5
- Fix kernel exception on userspace access to a currently disabled
coprocessor.
- Fix coprocessor data saving/restoring in configurations with multiple
coprocessors.
- Fix ptrace access to coprocessor data on configurations with multiple
coprocessors with high alignment requirements.
----------------------------------------------------------------
Max Filippov (3):
xtensa: enable coprocessors that are being flushed
xtensa: fix coprocessor context offset definitions
xtensa: fix coprocessor part of ptrace_{get,set}xregs
arch/xtensa/kernel/asm-offsets.c | 16 +++++++--------
arch/xtensa/kernel/process.c | 5 ++++-
arch/xtensa/kernel/ptrace.c | 42 ++++++++++++++++++++++++++++++++++++----
3 files changed, 50 insertions(+), 13 deletions(-)
Thanks.
-- Max
next reply other threads:[~2018-11-28 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 20:07 Max Filippov [this message]
2018-11-28 22:15 ` [PULL 0/3] Xtensa fixes for v4.20-rc5 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=20181128200716.29346-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).