[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150120102919.GP5767@x1>
Date: Tue, 20 Jan 2015 10:29:19 +0000
From: Lee Jones <lee.jones@...aro.org>
To: Robert Jarzmik <robert.jarzmik@...e.fr>
Cc: Rob Herring <robh+dt@...nel.org>, Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Daniel Mack <daniel@...que.org>,
Haojian Zhuang <haojian.zhuang@...il.com>,
Samuel Ortiz <sameo@...ux.intel.com>,
Arnd Bergmann <arnd@...db.de>,
Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board
On Mon, 19 Jan 2015, Robert Jarzmik wrote:
> Lee Jones <lee.jones@...aro.org> writes:
> > On Fri, 16 Jan 2015, Robert Jarzmik wrote:
[...]
> >> + res = platform_get_resource(pdev, IORESOURCE_IRQ, 0);
> >
> > platform_get_irq()?
> No. I need the flags.
Where are they used?
[...]
> >> + if (ret) {
> >> + dev_err(&pdev->dev, "Couldn't request main irq : ret = %d\n",
> >> + ret);
> >
> > I'm not keen on this type of formatting. Besides the system will
> > print out the returned error on failure.
> Well, it will print -EINVAL or -ENODEV. When I'll receive an request on the
> driver with -ENODEV, how will I know it will come from this request_irq() or
> another part of the code ... Well I can remove it if you want, but I think it's
> an error.
I'm not asking you to remove the entire message, just the junk at the
end.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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