From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] gpio: vt8500: memory cleanup missing
Date: Tue, 15 Jan 2013 18:20:20 +1300 [thread overview]
Message-ID: <1358227220.5928.2.camel@gitbox> (raw)
In-Reply-To: <1358188644-23838-1-git-send-email-linux@prisktech.co.nz>
On Tue, 2013-01-15 at 07:37 +1300, Tony Prisk wrote:
> This driver is missing a .remove callback, and the fail path on
> probe is incomplete.
>
> If an error occurs in vt8500_add_chips, gpio_base is not unmapped.
> The driver is also ignoring the return value from this function so
> if a chip fails to register it completes as successful.
>
> Replaced pr_err with dev_err in vt8500_add_chips since the device is
> available.
>
> There is also no .remove callback defined. To allow removing the
> registered chips, I have moved *vtchip to be a static global.
>
> Signed-off-by: Tony Prisk <linux@prisktech.co.nz>
> ---
> Hi Grant,
>
> Let me know what you think of these changes.
>
> v2:
> Removed unnecessary whitespace change.
> Removed test against pdev->dev.of_node (np). Replaced code with a
> devm_request_and_ioremap so np is now unneccessary. This also removes the need
> for cleanup in the fail path.
> Move struct vt8500_gpio_chip within vt8500_data and store the iobase and
> num_banks in vt8500_data.
>
Grant,
If there are no further changes for this patch, would you mind
correcting the commit message when you merge it?
-There is also no .remove callback defined. To allow removing the
-Registered chips, I have moved *vtchip to be a static global.
+ There is also no .remove callback defined.
Otherwise, I will fix it along with whatever other comments come in.
Regards
Tony P
next prev parent reply other threads:[~2013-01-15 5:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 18:37 [PATCH v2] gpio: vt8500: memory cleanup missing Tony Prisk
2013-01-15 5:20 ` Tony Prisk [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-10 19:09 Tony Prisk
2013-01-14 14:14 ` Grant Likely
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=1358227220.5928.2.camel@gitbox \
--to=linux@prisktech.co.nz \
--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).