From: Manish Badarkhe <badarkhe.manish@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: broonie@kernel.org, lgirdwood@gmail.com,
gregkh@linuxfoundation.org, badarkhe.manish@gmail.com
Subject: [PATCH V4 0/2] devm_* API operation for fixed regulator
Date: Wed, 29 Jan 2014 20:27:26 +0530 [thread overview]
Message-ID: <1391007448-26245-1-git-send-email-badarkhe.manish@gmail.com> (raw)
Use devm_* API operations for fixed regulator driver so that
driver core will manage resources.
Also, introduce a new API "devm_kstrdup" and used it in fixed
regulator driver to manage resources.
Changes since V3:
1. Update "devm_kstrdup" function to remove "size" argument.
Also,used "devm_kmalloc" instead of "devm_kzalloc".
Changes since V2:
1. Update driver to use new API "devm_kstrdup" instead of
"kstrdup".
2. Added a seperate patch to introduce new API "devm_kstrdup"
Changes since V1:
1. Updated driver to use "devm_kzalloc" instead of "kstrdup".
2. Updated commit message.
Manish Badarkhe (2):
devres: introduce API "devm_kstrdup"
regulator: fixed: update to devm_* API
drivers/base/devres.c | 26 ++++++++++++++++++++++++++
drivers/regulator/fixed.c | 42 ++++++++++++------------------------------
include/linux/device.h | 1 +
3 files changed, 39 insertions(+), 30 deletions(-)
--
1.7.10.4
next reply other threads:[~2014-01-29 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 14:57 Manish Badarkhe [this message]
2014-01-29 14:57 ` [PATCH V4 1/2] devres: introduce API "devm_kstrdup" Manish Badarkhe
2014-01-29 14:57 ` [PATCH V4 2/2] regulator: fixed: update to devm_* API Manish Badarkhe
2014-02-03 13:15 ` [PATCH V4 0/2] devm_* API operation for fixed regulator Manish Badarkhe
2014-02-04 13:12 ` Mark Brown
2014-02-11 16:34 ` Mark Brown
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=1391007448-26245-1-git-send-email-badarkhe.manish@gmail.com \
--to=badarkhe.manish@gmail.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--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
all inboxes | Powered by JetHome®