From: alex@digriz.org.uk (Alexander Clouter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 4/4] arm: orion5x: correct IRQ used in dtsi for mv_cesa
Date: Tue, 26 Mar 2013 21:02:07 +0000 [thread overview]
Message-ID: <20130326210207.GN7123@edkhil> (raw)
In-Reply-To: <20130325084739.GF5627@lunn.ch>
Hi,
On Mon, Mar 25, 2013 at 09:47:39AM +0100, Andrew Lunn wrote:
>On Sat, Mar 23, 2013 at 10:29:57PM +0000, Alexander Clouter wrote:
>> The crypto functionality hook in the orion5x dtsi uses an IRQ that clashes
>> with the Ethernet controller, so lets move it to use the IRQ that the non-DT
>> code utilises.
>
>Move is the wrong word here. The IRQ are hardware assigned, you cannot
>pick and choose. I would write a comment like:
>
>Fix the IRQ number for crypto, which should be 28, not 22 which is
>actually Ethernet.
>
No problem, wanging an updated patch out.
Cheers
--
Alexander Clouter
.sigmonster says: BOFH excuse #125:
we just switched to Sprint.
next prev parent reply other threads:[~2013-03-26 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 22:29 [PATCHv2 0/4] arm: orion5x: devicetree fixups and additions Alexander Clouter
2013-03-23 22:29 ` [PATCHv2 1/4] arm: orion5x: fix orion5x.dtsi gpio parameters Alexander Clouter
2013-03-25 8:43 ` Andrew Lunn
2013-03-26 21:02 ` Alexander Clouter
2013-03-23 22:29 ` [PATCHv2 2/4] arm: orion5x: add ehci bindings to dtsi Alexander Clouter
2013-03-23 22:29 ` [PATCHv2 3/4] arm: orion5x: enable xor for orion5x platform Alexander Clouter
2013-03-23 22:29 ` [PATCHv2 4/4] arm: orion5x: correct IRQ used in dtsi for mv_cesa Alexander Clouter
2013-03-25 8:47 ` Andrew Lunn
2013-03-26 21:02 ` Alexander Clouter [this message]
2013-03-24 9:48 ` [PATCHv2 0/4] arm: orion5x: devicetree fixups and additions Arnd Bergmann
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=20130326210207.GN7123@edkhil \
--to=alex@digriz.org.uk \
--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).