From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND] [PATCH 3.6.0- 5/6] ARM/omap: use module_platform_driver macro
Date: Fri, 14 Dec 2012 10:50:34 -0800 [thread overview]
Message-ID: <20121214185033.GH4989@atomide.com> (raw)
In-Reply-To: <1350025894-30625-1-git-send-email-srinivas.kandagatla@st.com>
* Srinivas KANDAGATLA <srinivas.kandagatla@st.com> [121012 00:14]:
> From: Srinivas Kandagatla <srinivas.kandagatla@st.com>
>
> This patch removes some code duplication by using
> module_platform_driver.
Thanks, applying this one into omap-for-v3.8/fixes-for-merge-window.
Skipping the mailbox ones as they are getting moved to live
under drivers. And the rng one should go via the rng maintainers.
Regards,
Tony
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@st.com>
> ---
> arch/arm/plat-omap/dmtimer.c | 13 +------------
> 1 files changed, 1 insertions(+), 12 deletions(-)
>
> diff --git a/arch/arm/plat-omap/dmtimer.c b/arch/arm/plat-omap/dmtimer.c
> index 938b50a..c89fc6a 100644
> --- a/arch/arm/plat-omap/dmtimer.c
> +++ b/arch/arm/plat-omap/dmtimer.c
> @@ -786,19 +786,8 @@ static struct platform_driver omap_dm_timer_driver = {
> },
> };
>
> -static int __init omap_dm_timer_driver_init(void)
> -{
> - return platform_driver_register(&omap_dm_timer_driver);
> -}
> -
> -static void __exit omap_dm_timer_driver_exit(void)
> -{
> - platform_driver_unregister(&omap_dm_timer_driver);
> -}
> -
> early_platform_init("earlytimer", &omap_dm_timer_driver);
> -module_init(omap_dm_timer_driver_init);
> -module_exit(omap_dm_timer_driver_exit);
> +module_platform_driver(omap_dm_timer_driver);
>
> MODULE_DESCRIPTION("OMAP Dual-Mode Timer Driver");
> MODULE_LICENSE("GPL");
> --
> 1.7.0.4
>
prev parent reply other threads:[~2012-12-14 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 7:11 [RESEND] [PATCH 3.6.0- 5/6] ARM/omap: use module_platform_driver macro Srinivas KANDAGATLA
2012-12-14 18:50 ` Tony Lindgren [this message]
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=20121214185033.GH4989@atomide.com \
--to=tony@atomide.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).