From: grfstrm@users.sourceforge.net (Anders Grafström)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/11] Thumb-2: Implementation of the unified start-up and exceptions code
Date: Mon, 15 Mar 2010 16:20:00 +0100 [thread overview]
Message-ID: <4B9E5020.2020706@users.sourceforge.net> (raw)
In-Reply-To: <alpine.LFD.2.00.1003121640280.31128@xanadu.home>
Nicolas Pitre wrote:
> On Fri, 12 Mar 2010, Russell King - ARM Linux wrote:
>
>> So yes, your patch is absolutely required - all ARMv5 and below are
>> facing a hazard as the kernel stands. It might explain some of the
>> weird behaviours people have been reporting as well.
>>
>> Please cleanup the description and submit to the patch system.
>
> And please add a small comment along side the otherwise seemingly
> useless nop.
Done.
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=5991/1
next prev parent reply other threads:[~2010-03-15 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090602130549.12732.15147.stgit@pc1117.cambridge.arm.com>
2010-03-12 17:30 ` [PATCH 03/11] Thumb-2: Implementation of the unified start-up and exceptions code Anders Grafström
2010-03-12 21:16 ` Russell King - ARM Linux
2010-03-12 21:44 ` Nicolas Pitre
2010-03-15 15:20 ` Anders Grafström [this message]
2010-03-15 15:43 ` Catalin Marinas
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=4B9E5020.2020706@users.sourceforge.net \
--to=grfstrm@users.sourceforge.net \
--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 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).