From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] arm: mvebu: fix resource leak
Date: Mon, 26 Aug 2013 19:36:55 +0800 [thread overview]
Message-ID: <1377517018-7716-1-git-send-email-jszhang@marvell.com> (raw)
These patches try to fix resource leak by adding missing of_node_put(),
iounmap or using devm_ioremap_resource() if available.
v4:
- re-generate since Ezequiel's patches add DT support to the
mvebu-mbus driver
v3:
- remove the clk patch since it's already taken by Mike
- Add more commit log as suggested by Ezequiel Garcia
v2:
- use devm_ioremap_resource() as suggested by Ezequiel Garcia
- use gates_out instead of bail_out as suggested by Mike Turquette
Jisheng Zhang (3):
arm: mvebu: add missing of_node_put() to fix reference leak
bus: mvebu: add missing of_node_put() to fix reference leak
pinctrl: mvebu: Convert to use devm_ioremap_resource
arch/arm/mach-mvebu/coherency.c | 8 +++++++-
arch/arm/mach-mvebu/platsmp.c | 1 +
arch/arm/mach-mvebu/pmsu.c | 1 +
arch/arm/mach-mvebu/system-controller.c | 1 +
drivers/bus/mvebu-mbus.c | 27 ++++++++++++++++++++-------
drivers/pinctrl/mvebu/pinctrl-mvebu.c | 11 +++++------
6 files changed, 35 insertions(+), 14 deletions(-)
--
1.8.4.rc3
next reply other threads:[~2013-08-26 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 11:36 Jisheng Zhang [this message]
2013-08-26 11:36 ` [PATCH v4 1/3] arm: mvebu: add missing of_node_put() to fix reference leak Jisheng Zhang
2013-08-26 11:36 ` [PATCH v4 2/3] bus: " Jisheng Zhang
2013-08-26 11:36 ` [PATCH v4 3/3] pinctrl: mvebu: Convert to use devm_ioremap_resource Jisheng Zhang
2013-08-26 20:46 ` Jason Cooper
2013-08-26 20:45 ` [PATCH v4 0/3] arm: mvebu: fix resource leak Jason Cooper
2013-08-27 3:01 ` Jisheng Zhang
2013-08-27 3:22 ` Jason Cooper
2013-08-27 3:27 ` Jisheng Zhang
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=1377517018-7716-1-git-send-email-jszhang@marvell.com \
--to=jszhang@marvell.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).