From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: linus.walleij@linaro.org, gnurou@gmail.com
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] Use devm_request_region
Date: Mon, 1 Feb 2016 18:54:25 -0500 [thread overview]
Message-ID: <cover.1454342087.git.vilhelm.gray@gmail.com> (raw)
By the time request_region is called in several GPIO drivers, a
corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
William Breathitt Gray (7):
gpio: 104-dio-48e: Use devm_request_region
gpio: 104-idi-48: Use devm_request_region
gpio: 104-idio-16: Use devm_request_region
gpio: amd8111: Use devm_request_region
gpio: ich: Use devm_request_region
gpio: sch311x: Use devm_request_region
gpio: ws16c48: Use devm_request_region
drivers/gpio/gpio-104-dio-48e.c | 22 +++++++-----------
drivers/gpio/gpio-104-idi-48.c | 22 +++++++-----------
drivers/gpio/gpio-104-idio-16.c | 22 +++++++-----------
drivers/gpio/gpio-amd8111.c | 7 +++---
drivers/gpio/gpio-ich.c | 51 ++++++++---------------------------------
drivers/gpio/gpio-sch311x.c | 7 +++---
drivers/gpio/gpio-ws16c48.c | 22 +++++++-----------
7 files changed, 47 insertions(+), 106 deletions(-)
--
2.4.10
next reply other threads:[~2016-02-01 23:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 23:54 William Breathitt Gray [this message]
2016-02-01 23:54 ` [PATCH 1/7] gpio: 104-dio-48e: Use devm_request_region William Breathitt Gray
2016-02-01 23:54 ` [PATCH 2/7] gpio: 104-idi-48: " William Breathitt Gray
2016-02-01 23:54 ` [PATCH 3/7] gpio: 104-idio-16: " William Breathitt Gray
2016-02-01 23:54 ` [PATCH 4/7] gpio: amd8111: " William Breathitt Gray
2016-02-01 23:54 ` [PATCH 5/7] gpio: ich: " William Breathitt Gray
2016-02-01 23:56 ` [PATCH 6/7] gpio: sch311x: " William Breathitt Gray
2016-02-02 0:11 ` kbuild test robot
2016-02-01 23:57 ` [PATCH 7/7] gpio: ws16c48: " William Breathitt Gray
2016-02-03 0:26 ` [PATCH 0/7] " Alexandre Courbot
2016-02-03 0:46 ` William Breathitt Gray
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=cover.1454342087.git.vilhelm.gray@gmail.com \
--to=vilhelm.gray@gmail.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).