From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clocksource: sirf: Remove unused variable
Date: Mon, 15 Dec 2014 17:17:58 +0100 [thread overview]
Message-ID: <548F09B6.6010202@linaro.org> (raw)
In-Reply-To: <1418659160-2115-1-git-send-email-thierry.reding@gmail.com>
On 12/15/2014 04:59 PM, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Commit ef89af1f4380 ("clocksource: sirf: Remove hard-coded clock rate")
> removes all uses of the timer_div variable. Since the variable is no
> longer used it should be removed.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
Applied to my tree. Thanks!
-- Daniel
--
<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
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Thierry Reding <thierry.reding@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Barry Song <baohua@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clocksource: sirf: Remove unused variable
Date: Mon, 15 Dec 2014 17:17:58 +0100 [thread overview]
Message-ID: <548F09B6.6010202@linaro.org> (raw)
In-Reply-To: <1418659160-2115-1-git-send-email-thierry.reding@gmail.com>
On 12/15/2014 04:59 PM, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Commit ef89af1f4380 ("clocksource: sirf: Remove hard-coded clock rate")
> removes all uses of the timer_div variable. Since the variable is no
> longer used it should be removed.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
Applied to my tree. Thanks!
-- Daniel
--
<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:[~2014-12-15 16:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 15:59 [PATCH] clocksource: sirf: Remove unused variable Thierry Reding
2014-12-15 15:59 ` Thierry Reding
2014-12-15 16:17 ` Daniel Lezcano [this message]
2014-12-15 16:17 ` Daniel Lezcano
2015-01-11 15:58 ` Barry Song
2015-01-11 15:58 ` Barry Song
2015-01-11 20:51 ` Daniel Lezcano
2015-01-11 20:51 ` Daniel Lezcano
-- strict thread matches above, loose matches on Subject: below --
2014-12-23 21:33 Fabio Estevam
2015-01-11 14:45 ` Barry Song
2015-01-13 14:22 [PATCH] clocksource: sirf: remove " Arnd Bergmann
2015-01-13 14:22 ` Arnd Bergmann
2015-01-13 14:27 ` Daniel Lezcano
2015-01-13 14:27 ` Daniel Lezcano
2015-01-13 15:24 ` Arnd Bergmann
2015-01-13 15:24 ` Arnd Bergmann
2015-01-13 15:39 ` Daniel Lezcano
2015-01-13 15:39 ` Daniel Lezcano
2015-01-13 15:24 ` Barry Song
2015-01-13 15:24 ` Barry Song
2015-01-13 16:22 ` Arnd Bergmann
2015-01-13 16:22 ` Arnd Bergmann
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=548F09B6.6010202@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 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.