From: wellsk40@gmail.com (Kevin Wells)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] input/touch: Introduce the LPC32xx touchscreen controller driver
Date: Fri, 13 Aug 2010 12:00:33 -0700 [thread overview]
Message-ID: <AANLkTik0voaTUHoJuaVGvmhqpUh_tfbk3VUNXyWMh1av@mail.gmail.com> (raw)
In-Reply-To: <20100813083311.GA7824@core.coreip.homeip.net>
>>
>> This patch set introduces support for the LPC32xx touchscreen
>> controller driver. The LPC32xx touchscreen controller supports
>> automated event detection and X/Y data conversion for resistive
>> touchscreens.
>>
>
> Overall looks very nice, a few comments below.
>
Thanks for helping review this driver. I'll update and repost once
the fixes and changes are finalized.
>> +
>> + ? ? if (input_register_device(tsc->dev)) {
>> + ? ? ? ? ? ? dev_err(&pdev->dev, "failed registering input device\n");
>> + ? ? ? ? ? ? goto err_stop_clk;
>
> retval is garbage here, you need to do:
>
> ? ? ? ?error = input_register_device();
> ? ? ? ?if (error) {
> ? ? ? ? ? ? ? ?...
> ? ? ? ? ? ? ? ?goto err_stop_clk;
> ? ? ? ?}
>
> I must say that I do not like mixing devm_* with the standard error path
> unwinding, if we can rely on devm_xxx() calls to take care of everything
> we should revert to standard error unsinding practice for everythng.
>
Would it be preferable to just use standard resource functions and error
path unwinding (with fixes in _remove too) similar to the other drivers in
./drivers/input?
next prev parent reply other threads:[~2010-08-13 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 23:09 rfc input/touch: LPC32xx: Introduce touch driver for the LPC32xx wellsk40 at gmail.com
2010-08-11 23:09 ` [PATCH] input/touch: Introduce the LPC32xx touchscreen controller driver wellsk40 at gmail.com
2010-08-13 8:33 ` Dmitry Torokhov
2010-08-13 19:00 ` Kevin Wells [this message]
2010-08-13 19:24 ` Dmitry Torokhov
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=AANLkTik0voaTUHoJuaVGvmhqpUh_tfbk3VUNXyWMh1av@mail.gmail.com \
--to=wellsk40@gmail.com \
--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).