From: Rob Jones <rob.jones@codethink.co.uk>
To: linus.walleij@linaro.org, gnurou@gmail.com
Cc: lgirdwood@gmail.com, broonie@kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel@codethink.co.uk, ian.molton@codethink.co.uk,
ben.dooks@codethink.co.uk, heiko@sntech.de,
rob.jones@codethink.co.uk
Subject: [PATCH V2 0/3] Change gpio_regulator_probe() to use managed resources.
Date: Wed, 2 Jul 2014 11:05:48 +0100 [thread overview]
Message-ID: <1404295551-13470-1-git-send-email-rob.jones@codethink.co.uk> (raw)
Extend the use of managed resource functions in regulator by replacing
all calls to unmanaged resource allocation functions in
gpio_regulator_probe() with their managed equivalent.
Add a new function, devm_kmemdup(), to drivers/base/devres.c to support this.
Rob Jones (3):
base: Add block copy func. for managed devices
gpio: allow gpio array requests for managed devices
regulator: use managed resources for gpio_regulator_probe().
drivers/base/devres.c | 25 +++++++++++++
drivers/gpio/devres.c | 63 ++++++++++++++++++++++++++++++++
drivers/regulator/gpio-regulator.c | 70 ++++++++++++------------------------
include/linux/device.h | 2 ++
include/linux/gpio.h | 4 +++
5 files changed, 117 insertions(+), 47 deletions(-)
--
1.7.10.4
Incorporates requested changes.
Note that this patch series no longer includes a change to devm_kstrdup()
as this was not essential to the primary aim of the series. This will be
submitted later once devm_kmemdup() has been accepted.
next reply other threads:[~2014-07-02 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 10:05 Rob Jones [this message]
2014-07-02 10:05 ` [PATCH V2 1/3] base: Add block copy func. for managed devices Rob Jones
2014-07-02 10:05 ` [PATCH V2 2/3] gpio: allow gpio array requests " Rob Jones
2014-07-04 23:12 ` Linus Walleij
2014-07-02 10:05 ` [PATCH V2 3/3] regulator: use managed resources for gpio_regulator_probe() Rob Jones
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=1404295551-13470-1-git-send-email-rob.jones@codethink.co.uk \
--to=rob.jones@codethink.co.uk \
--cc=ben.dooks@codethink.co.uk \
--cc=broonie@kernel.org \
--cc=gnurou@gmail.com \
--cc=heiko@sntech.de \
--cc=ian.molton@codethink.co.uk \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@codethink.co.uk \
--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).