Re: [PATCH] fix UIO with device tree but no assigned interrupt

[Greg Kroah-Hartman]

On Tue, Jun 18, 2013 at 04:26:34PM +0200, Pavel Machek wrote:
> 
> If device is initialized from device tree, but has no interrupt
> assigned, uio will still try to request and interrupt old way,
> fails, and fails registration.
> 
> This is wrong; don't try initializing irq using platform data if
> device tree is available.
> 
> Simplified code based on suggestion by Grant Likely.
> 
> Fixed memory leak in "irq can not be registered" error path.
> 
> Signed-off-by: Pavel Machek <pavel@xxxxxxx>
> Reported-by: Detlev Zundel <dzu@xxxxxxx>

I see a ton of patches in this thread, and have no idea which one is
"newest" and correct.

Please resend, in a format that I do not have to edit at all (hint, the
subject line counts), that I can apply properly.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/