From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/6] clk: sunxi: Move the 24M oscillator to a file of its own
Date: Sun, 11 May 2014 06:35:05 +0200 [thread overview]
Message-ID: <20140511043505.GO7047@lukather> (raw)
In-Reply-To: <536E57EE.2030401@elopez.com.ar>
On Sat, May 10, 2014 at 01:46:38PM -0300, Emilio L?pez wrote:
There was probably something interesting here, but both the messages
you sent are full of empty :)
--
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/20140511/dd6f78a8/attachment.sig>
next prev parent reply other threads:[~2014-05-11 4:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 3:33 [PATCH 0/6] sunxi: clk: Various cleanup and rework Maxime Ripard
2014-05-10 3:33 ` [PATCH 1/6] clk: sunxi: Remove calls to clk_put Maxime Ripard
2014-05-10 3:33 ` [PATCH 2/6] clk: sunxi: Move the 24M oscillator to a file of its own Maxime Ripard
2014-05-10 16:13 ` Emilio López
2014-05-10 16:46 ` Emilio López
2014-05-11 4:35 ` Maxime Ripard [this message]
2014-05-11 4:44 ` Emilio López
2014-05-10 3:33 ` [PATCH 3/6] clk: sunxi: Move the GMAC clock " Maxime Ripard
2014-05-10 17:07 ` [linux-sunxi] " Emilio López
2014-05-12 19:36 ` Maxime Ripard
2014-05-12 19:45 ` Emilio López
2014-05-12 20:54 ` Maxime Ripard
2014-05-10 3:33 ` [PATCH 4/6] clk: sunxi: Rework clock protection code Maxime Ripard
2014-05-10 3:33 ` [PATCH 5/6] clk: sun6i: Protect CPU clock Maxime Ripard
2014-05-10 3:33 ` [PATCH 6/6] clk: sun6i: Protect SDRAM gating bit Maxime Ripard
2014-05-10 17:22 ` [linux-sunxi] [PATCH 0/6] sunxi: clk: Various cleanup and rework Emilio López
2014-05-13 1:12 ` Mike Turquette
2014-05-15 15:10 ` Emilio López
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=20140511043505.GO7047@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.