From: Max Filippov <jcmvbkbc@gmail.com>
To: Chris Zankel <chris@zankel.net>
Cc: Marc Gauthier <marc@tensilica.com>,
linux-xtensa@linux-xtensa.org, linux-arch@vger.kernel.org,
Max Filippov <jcmvbkbc@gmail.com>
Subject: [PATCHv2 0/2] xtensa fixes for 3.12
Date: Sat, 26 Oct 2013 05:03:03 +0400 [thread overview]
Message-ID: <1382749385-29062-1-git-send-email-jcmvbkbc@gmail.com> (raw)
Hi Chris,
This is the second version of late 3.12 fixes, changes v1->v2:
xtensa: fix fast_syscall_spill_registers_fixup: set windowstart bit for
the current register frame in the fast_syscall_spill_registers_fixup;
expand comments, add FIXME mark.
xtensa: don't use alternate signal stack on threads: no changes.
I can post the third version if using a1 instead of a2 in the
_spill_registers .Lc12 is fine.
You can pull these changes from my git tree,
the following changes since commit 61e6cfa80de5760bbe406f4e815b7739205754d2:
Linux 3.12-rc5 (2013-10-13 15:41:28 -0700)
are available in the git repository at:
git://github.com/jcmvbkbc/linux-xtensa.git xtensa-fixes-for-upstream
for you to fetch changes up to cbcc64e11437f701121e71ca55ff0eb9815af530:
xtensa: don't use alternate signal stack on threads (2013-10-26 04:39:13 +0400)
----------------------------------------------------------------
Baruch Siach (1):
xtensa: don't use alternate signal stack on threads
Max Filippov (1):
xtensa: fix fast_syscall_spill_registers_fixup
arch/xtensa/kernel/entry.S | 64 +++++++++++++++++++++++++++++++--------------
arch/xtensa/kernel/signal.c | 2 +-
2 files changed, 46 insertions(+), 20 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-10-26 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 1:03 Max Filippov [this message]
2013-10-26 1:03 ` [PATCHv2 1/2] xtensa: fix fast_syscall_spill_registers_fixup Max Filippov
2013-10-26 1:03 ` [PATCHv2 2/2] xtensa: don't use alternate signal stack on threads Max Filippov
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=1382749385-29062-1-git-send-email-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=chris@zankel.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=marc@tensilica.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.