From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Gupta, Ramesh" <grgupta@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/1] Export notifier register functions for kernel module building
Date: Thu, 12 Feb 2009 09:48:04 -0800 [thread overview]
Message-ID: <878wobpmwb.fsf@deeprootsystems.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02A40C1020@dbde02.ent.ti.com> (Ramesh Gupta's message of "Thu\, 12 Feb 2009 14\:50\:56 +0530")
"Gupta, Ramesh" <grgupta@ti.com> writes:
> This Patch exports symbols clk_notifier_register/unregister
> function for other kernel modules usage.
>
> Signed-off-by: Ramesh Gupta G <grgupta@ti.com>
Thanks, pushed to PM branch.
Kevin
> ---
> arch/arm/plat-omap/clock.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/plat-omap/clock.c b/arch/arm/plat-omap/clock.c
> index e0940a1..c8d9e96 100644
> --- a/arch/arm/plat-omap/clock.c
> +++ b/arch/arm/plat-omap/clock.c
> @@ -680,6 +680,7 @@ int clk_notifier_register(struct clk *clk, struct notifier_block *nb)
>
> return r;
> }
> +EXPORT_SYMBOL(clk_notifier_register);
>
> /**
> * clk_notifier_unregister - remove a clock change notifier
> @@ -735,6 +736,7 @@ int clk_notifier_unregister(struct clk *clk, struct notifier_block *nb)
>
> return r;
> }
> +EXPORT_SYMBOL(clk_notifier_unregister);
>
>
>
> --
> 1.5.3.2
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-12 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 9:20 [PATCH 1/1] Export notifier register functions for kernel module building Gupta, Ramesh
2009-02-12 17:48 ` Kevin Hilman [this message]
2009-03-24 9:28 ` Paul Walmsley
2009-03-24 9:42 ` Gupta, Ramesh
2009-03-24 9:48 ` Paul Walmsley
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=878wobpmwb.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=grgupta@ti.com \
--cc=linux-omap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.