From: linus.walleij@stericsson.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Common struct clk implementation, v5
Date: Mon, 21 Jun 2010 09:54:01 +0200 [thread overview]
Message-ID: <AANLkTikBESJzzQ87AzVg7ZBB3ygbWXK4aw3u0xSJSJi2@mail.gmail.com> (raw)
In-Reply-To: <1277098513.947165.104554431018.0.gpush@pororo>
2010/6/21 Jeremy Kerr <jeremy.kerr@canonical.com>:
> Comments most welcome.
I think this is a step in the right direction, if it gets merged I will switch
the U300 over to it.
Yours,
Linus Walleij
prev parent reply other threads:[~2010-06-21 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 5:35 [PATCH 0/2] Common struct clk implementation, v5 Jeremy Kerr
2010-06-21 5:35 ` [PATCH 2/2] clk: Generic support for fixed-rate clocks Jeremy Kerr
2010-06-21 20:43 ` Ryan Mallon
2010-06-22 1:05 ` Jeremy Kerr
2010-06-21 5:35 ` [PATCH 1/2] Add a common struct clk Jeremy Kerr
2010-06-22 4:43 ` Baruch Siach
2010-07-05 2:33 ` MyungJoo Ham
2010-07-12 2:19 ` Jeremy Kerr
2010-06-21 7:54 ` Linus Walleij [this message]
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=AANLkTikBESJzzQ87AzVg7ZBB3ygbWXK4aw3u0xSJSJi2@mail.gmail.com \
--to=linus.walleij@stericsson.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 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).