[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwGFogD4ROCH9m=c2jqB2axvrH-dnKPtA8kxXL9b3CVBw@mail.gmail.com>
Date: Tue, 6 Dec 2011 13:25:07 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Rob Herring <robherring2@...il.com>
Cc: Anton Vorontsov <cbouatmailru@...il.com>,
Ingo Molnar <mingo@...e.hu>, Jeff Garzik <jgarzik@...hat.com>,
Grant Likely <grant.likely@...retlab.ca>,
Stephen Rothwell <sfr@...b.auug.org.au>,
devicetree-discuss@...ts.ozlabs.org,
LKML <linux-kernel@...r.kernel.org>, linux-ide@...r.kernel.org,
Randy Dunlap <rdunlap@...otime.net>,
linux-next@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH 1/2] of/irq: Get rid of NO_IRQ usage
On Tue, Dec 6, 2011 at 1:22 PM, Rob Herring <robherring2@...il.com> wrote:
>
> This warning code is really ugly. Can we just drop it? In my searching
> of in kernel dts files, there's only 1 instance I have found (Versatile
> AB watchdog) that would hit this.
I do agree. Especially since we never got any input on whether it works or not.
> If not, you don't need to handle irq_create_of_mapping return as that is
> already always 0 for no irq or error.
Yeah, I'd like to just remove NO_IRQ from the OF paths. Afaik, it
hasn't worked as NO_IRQ before anyway, so even if the rest of the
drivers end up continuing using NO_IRQ, the OF-enabled ones on ARM
should just stop. There can't be many of those yet.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists