From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: add INTC out of memory error handling
Date: Tue, 23 Mar 2010 08:55:01 +0000 [thread overview]
Message-ID: <20100323085501.GE30655@linux-sh.org> (raw)
In-Reply-To: <20100310093101.5422.38371.sendpatchset@t400s>
On Wed, Mar 10, 2010 at 06:31:01PM +0900, Magnus Damm wrote:
> Extend the INTC code to warn and return an error code
> in the case of memory allocation failure.
On Wed, Mar 10, 2010 at 06:38:55PM +0900, Magnus Damm wrote:
> Extend the INTC code with ioremap() support V2.
>
> Support INTC controllers that are not accessible through
> a 1:1 virt:phys window. Needed by SH-Mobile ARM INTCS.
>
> The INTC code behaves as usual if the io window resource
> is omitted. The slow phys->virt lookup only happens during
> setup. The fast path code operates on virtual addresses.
Both applied to the sh/intc-extension topic branch, thanks.
prev parent reply other threads:[~2010-03-23 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 9:31 [PATCH] sh: add INTC out of memory error handling Magnus Damm
2010-03-23 8:55 ` Paul Mundt [this message]
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=20100323085501.GE30655@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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).