From: tim.zhang@spreadtrum.com (Yang Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] arm: Early IRQ enabling in the Undef user handler
Date: Mon, 31 Mar 2014 04:11:26 +0000 (UTC) [thread overview]
Message-ID: <loom.20140331T053123-366@post.gmane.org> (raw)
In-Reply-To: 1377689664-27614-1-git-send-email-catalin.marinas@arm.com
Catalin Marinas <catalin.marinas <at> arm.com> writes:
> (an alternative simpler patch would be to enable the interrupts only
> around the user access instructions in __und_usr and disable them
> afterwards, so I would rather do it as in this series).
Tested-by: Yang Zhang<email:tim.zhang@spreadtrum.com>
next prev parent reply other threads:[~2014-03-31 4:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 11:34 [PATCH 0/5] arm: Early IRQ enabling in the Undef user handler Catalin Marinas
2013-08-28 11:34 ` [PATCH 1/5] arm: Move asm macro get_thread_info to asm/assembler.h Catalin Marinas
2013-08-28 11:34 ` [PATCH 2/5] arm: Add {inc,dec}_preempt_count asm macros Catalin Marinas
2013-08-28 11:34 ` [PATCH 3/5] arm: Disable preemption in iwmmxt_task_enable() Catalin Marinas
2013-08-28 11:34 ` [PATCH 4/5] arm: Disable preemption in crunch_task_enable() Catalin Marinas
2013-08-28 11:34 ` [PATCH 5/5] arm: Enable IRQs before attempting to read user space in __und_usr Catalin Marinas
2013-11-21 9:35 ` Alexey Ignatov
2013-11-21 10:29 ` Russell King - ARM Linux
2013-11-22 9:47 ` Alexey Ignatov
2014-03-31 4:11 ` Yang Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-13 18:15 [PATCH 0/5] arm: Early IRQ enabling in the Undef user handler Catalin Marinas
2014-04-01 12:03 ` Arun KS
2014-04-01 15:41 ` Catalin Marinas
2014-04-02 4:03 ` Arun KS
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=loom.20140331T053123-366@post.gmane.org \
--to=tim.zhang@spreadtrum.com \
--cc=linux-arm-kernel@lists.infradead.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 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.