From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv4 08/10] clocksource: sun4i: Remove TIMER_SCAL variable
Date: Sat, 6 Jul 2013 10:10:45 +0200 [thread overview]
Message-ID: <20130706081045.GY2959@lukather> (raw)
In-Reply-To: <alpine.DEB.2.02.1307060031030.32106@ionos.tec.linutronix.de>
On Sat, Jul 06, 2013 at 01:17:41AM +0200, Thomas Gleixner wrote:
> I really recommend that you go out for lots of beer/wine NOW and
> resume reading this mail when you recovered from that.
>
> I definitely appreciate your responsivness to feedback, but please go
> back and read my reply to the previous version of this patch
> carefully. You might eventually find out that I pointed you to another
> redundant clk_get_rate() call in that code.
>
> After you did this, please go through the other patches in that series
> and check how many new instances of clk_get_rate() calls you add down
> the road. I did not even bother to look whether you cleaned it up
> between v3 and v4, but I'm quite sure you did not. If I'm wrong, I owe
> you a beer at the next conference.
Wow, you really want me to drink, do you? :)
Actually, I did clean up. The other user you spotted that was previously
introduced in the patch 4/10, and if you take a look at it, you'll see
that it actually uses the rate variable like you suggested.
Now, your mail made me realize that patch 10 introduced a direct
clk_get_rate call, that I forgot to cleanup. After applying these
patches, it's the only user left.
I'll send a v5. Do you have any additionnal comments on those patches to
avoid wasting more electrons?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130706/6af8767a/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: John Stultz <john.stultz@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Emilio Lopez <emilio@elopez.com.ar>,
kevin.z.m.zh@gmail.com, sunny@allwinnertech.com,
shuge@allwinnertech.com, linux-sunxi@googlegroups.com
Subject: Re: [PATCHv4 08/10] clocksource: sun4i: Remove TIMER_SCAL variable
Date: Sat, 6 Jul 2013 10:10:45 +0200 [thread overview]
Message-ID: <20130706081045.GY2959@lukather> (raw)
In-Reply-To: <alpine.DEB.2.02.1307060031030.32106@ionos.tec.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
On Sat, Jul 06, 2013 at 01:17:41AM +0200, Thomas Gleixner wrote:
> I really recommend that you go out for lots of beer/wine NOW and
> resume reading this mail when you recovered from that.
>
> I definitely appreciate your responsivness to feedback, but please go
> back and read my reply to the previous version of this patch
> carefully. You might eventually find out that I pointed you to another
> redundant clk_get_rate() call in that code.
>
> After you did this, please go through the other patches in that series
> and check how many new instances of clk_get_rate() calls you add down
> the road. I did not even bother to look whether you cleaned it up
> between v3 and v4, but I'm quite sure you did not. If I'm wrong, I owe
> you a beer at the next conference.
Wow, you really want me to drink, do you? :)
Actually, I did clean up. The other user you spotted that was previously
introduced in the patch 4/10, and if you take a look at it, you'll see
that it actually uses the rate variable like you suggested.
Now, your mail made me realize that patch 10 introduced a direct
clk_get_rate call, that I forgot to cleanup. After applying these
patches, it's the only user left.
I'll send a v5. Do you have any additionnal comments on those patches to
avoid wasting more electrons?
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-06 8:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 22:18 [PATCHv4 00/10] clocksource: sunxi: Timer fixes and cleanup Maxime Ripard
2013-07-05 22:18 ` Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 01/10] clocksource: sun4i: Use the BIT macros where possible Maxime Ripard
2013-07-05 22:18 ` Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 02/10] clocksource: sun4i: Wrap macros arguments in parenthesis Maxime Ripard
2013-07-05 22:18 ` Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 03/10] clocksource: sun4i: rename AUTORELOAD define to RELOAD Maxime Ripard
2013-07-05 22:18 ` Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 04/10] clocksource: sun4i: Add clocksource and sched clock drivers Maxime Ripard
2013-07-05 22:18 ` Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 05/10] clocksource: sun4i: Don't forget to enable the clock we use Maxime Ripard
2013-07-05 22:18 ` Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 06/10] clocksource: sun4i: Fix the next event code Maxime Ripard
2013-07-05 22:18 ` Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 07/10] clocksource: sun4i: Factor out some timer code Maxime Ripard
2013-07-05 22:18 ` Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 08/10] clocksource: sun4i: Remove TIMER_SCAL variable Maxime Ripard
2013-07-05 22:18 ` Maxime Ripard
2013-07-05 23:17 ` Thomas Gleixner
2013-07-05 23:17 ` Thomas Gleixner
2013-07-06 8:10 ` Maxime Ripard [this message]
2013-07-06 8:10 ` Maxime Ripard
2013-07-06 9:16 ` [linux-sunxi] " Oliver Schinagl
2013-07-06 9:16 ` Oliver Schinagl
2013-07-06 10:56 ` Arnd Bergmann
2013-07-06 10:56 ` Arnd Bergmann
2013-07-06 21:07 ` Thomas Gleixner
2013-07-06 21:07 ` Thomas Gleixner
2013-07-05 22:18 ` [PATCHv4 09/10] clocksource: sun4i: Cleanup parent clock setup Maxime Ripard
2013-07-05 22:18 ` Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 10/10] clocksource: sun4i: Fix bug when switching from periodic to oneshot modes Maxime Ripard
2013-07-05 22:18 ` Maxime Ripard
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=20130706081045.GY2959@lukather \
--to=maxime.ripard@free-electrons.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 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.