From: oliver+list@schinagl.nl (Oliver Schinagl)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [PATCHv4 08/10] clocksource: sun4i: Remove TIMER_SCAL variable
Date: Sat, 06 Jul 2013 11:16:51 +0200 [thread overview]
Message-ID: <51D7E083.1090109@schinagl.nl> (raw)
In-Reply-To: <20130706081045.GY2959@lukather>
On 06-07-13 10:10, Maxime Ripard wrote:
>
> I'll send a v5. Do you have any additionnal comments on those patches to
> avoid wasting more electrons?
Pff, we all know Maxime's electrons are free
>
> Maxime
>
next prev parent reply other threads:[~2013-07-06 9:16 UTC|newest]
Thread overview: 16+ 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 ` [PATCHv4 01/10] clocksource: sun4i: Use the BIT macros where possible Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 02/10] clocksource: sun4i: Wrap macros arguments in parenthesis Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 03/10] clocksource: sun4i: rename AUTORELOAD define to RELOAD 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 ` [PATCHv4 05/10] clocksource: sun4i: Don't forget to enable the clock we use Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 06/10] clocksource: sun4i: Fix the next event code Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 07/10] clocksource: sun4i: Factor out some timer code Maxime Ripard
2013-07-05 22:18 ` [PATCHv4 08/10] clocksource: sun4i: Remove TIMER_SCAL variable Maxime Ripard
2013-07-05 23:17 ` Thomas Gleixner
2013-07-06 8:10 ` Maxime Ripard
2013-07-06 9:16 ` Oliver Schinagl [this message]
2013-07-06 10:56 ` [linux-sunxi] " Arnd Bergmann
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 ` [PATCHv4 10/10] clocksource: sun4i: Fix bug when switching from periodic to oneshot modes 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=51D7E083.1090109@schinagl.nl \
--to=oliver+list@schinagl.nl \
--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