From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] clocksource: exynos_mct: Staticize struct clocksource
Date: Mon, 11 May 2015 16:06:02 +0200 [thread overview]
Message-ID: <5550B74A.8010607@linaro.org> (raw)
In-Reply-To: <1430368973-23786-2-git-send-email-k.kozlowski@samsung.com>
On 04/30/2015 06:42 AM, Krzysztof Kozlowski wrote:
> The struct clocksource 'mct_frc' is not exported and used outside so
> make it static.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> ---
Applied to my tree for 4.2
-- Daniel
> drivers/clocksource/exynos_mct.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clocksource/exynos_mct.c b/drivers/clocksource/exynos_mct.c
> index 87c2e558c465..8b2a9fc66dcc 100644
> --- a/drivers/clocksource/exynos_mct.c
> +++ b/drivers/clocksource/exynos_mct.c
> @@ -209,7 +209,7 @@ static void exynos4_frc_resume(struct clocksource *cs)
> exynos4_mct_frc_start();
> }
>
> -struct clocksource mct_frc = {
> +static struct clocksource mct_frc = {
> .name = "mct-frc",
> .rating = 400,
> .read = exynos4_frc_read,
>
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2015-05-11 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 4:42 [PATCH 1/3] clocksource: exynos_mct: Change exynos4_mct_tick_clear return type to void Krzysztof Kozlowski
2015-04-30 4:42 ` [PATCH 2/3] clocksource: exynos_mct: Staticize struct clocksource Krzysztof Kozlowski
2015-05-11 14:06 ` Daniel Lezcano [this message]
2015-04-30 4:42 ` [PATCH 3/3] clocksource: exynos_mct: Remove old platform mct_init() Krzysztof Kozlowski
2015-05-11 14:06 ` Daniel Lezcano
2015-05-11 14:05 ` [PATCH 1/3] clocksource: exynos_mct: Change exynos4_mct_tick_clear return type to void Daniel Lezcano
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=5550B74A.8010607@linaro.org \
--to=daniel.lezcano@linaro.org \
--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).