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/4] xtensa fixes for v5.1-rc5
Date: Mon, 8 Apr 2019 11:01:46 -0700 [thread overview]
Message-ID: <20190408180146.20202-1-jcmvbkbc@gmail.com> (raw)
Hi Linus,
please pull the following batch of fixes for the xtensa architecture:
The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6:
Linux 5.1-rc3 (2019-03-31 14:39:29 -0700)
are available in the git repository at:
git://github.com/jcmvbkbc/linux-xtensa.git tags/xtensa-20190408
for you to fetch changes up to ecae26fae15abb7d433557afbd15467ce1c444f5:
xtensa: fix format string warning in init_pmd (2019-04-04 18:45:55 -0700)
----------------------------------------------------------------
xtensa fixes for v5.1-rc5
- fix syscall number passed to trace_sys_exit;
- fix syscall number initialization in start_thread;
- fix level interpretation in the return_address;
- fix format string warning in init_pmd.
----------------------------------------------------------------
Max Filippov (4):
xtensa: use actual syscall number in do_syscall_trace_leave
xtensa: fix initialization of pt_regs::syscall in start_thread
xtensa: fix return_address
xtensa: fix format string warning in init_pmd
arch/xtensa/include/asm/processor.h | 21 ++++++++++++---------
arch/xtensa/kernel/entry.S | 6 ++++++
arch/xtensa/kernel/stacktrace.c | 6 +++++-
arch/xtensa/mm/mmu.c | 2 +-
4 files changed, 24 insertions(+), 11 deletions(-)
--
Thanks.
-- Max
next reply other threads:[~2019-04-08 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 18:01 Max Filippov [this message]
2019-04-09 3:15 ` [PULL 0/4] xtensa fixes for v5.1-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=20190408180146.20202-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).