From: Tushar Behera <tushar.behera-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: [PATCH V3 0/4] i2c: s3c2410: Add devm_* apis and cleanup
Date: Thu, 24 Jan 2013 15:41:05 +0530 [thread overview]
Message-ID: <1359022269-12593-1-git-send-email-tushar.behera@linaro.org> (raw)
This patchset cleans up the probe function of i2c-s3c2410 driver.
These have been tested on Exynos4210 based Origen board.
Changes since V2:
* Rebased to v3.8-rc4.
* devm_request_and_ioremap() has already been implemented.
Changes since V1:
* devm_request_mem_region and devm_ioremap calls were replaced by
devm_request_and_ioremap() call.
* All devm_* related modifications (earlier patches 2-5) were merged
to a single patch.
Tushar Behera (4):
i2c: s3c2410: Remove unnecessary label err_noclk
i2c: s3c2410: Convert to use devm_* APIs
i2c: s3c2410: Move location of clk_prepare_enable() call in probe
function
i2c: s3c2410: Remove err_cpufreq label
drivers/i2c/busses/i2c-s3c2410.c | 59 +++++++++++++------------------------
1 files changed, 21 insertions(+), 38 deletions(-)
--
1.7.4.1
next reply other threads:[~2013-01-24 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 10:11 Tushar Behera [this message]
2013-01-24 10:11 ` [PATCH V3 1/4] i2c: s3c2410: Remove unnecessary label err_noclk Tushar Behera
[not found] ` <1359022269-12593-1-git-send-email-tushar.behera-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-01-24 10:11 ` [PATCH V3 2/4] i2c: s3c2410: Convert to use devm_* APIs Tushar Behera
2013-01-24 10:11 ` [PATCH V3 3/4] i2c: s3c2410: Move location of clk_prepare_enable() call in probe function Tushar Behera
2013-01-24 10:11 ` [PATCH V3 4/4] i2c: s3c2410: Remove err_cpufreq label Tushar Behera
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=1359022269-12593-1-git-send-email-tushar.behera@linaro.org \
--to=tushar.behera-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=patches-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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).