From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Common clock API for i.MX
Date: Wed, 25 Jan 2012 15:52:02 +0000 [thread overview]
Message-ID: <20120125155202.GQ3687@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1201251040040.2759@xanadu.home>
On Wed, Jan 25, 2012 at 10:42:20AM -0500, Nicolas Pitre wrote:
> On Wed, 25 Jan 2012, Mark Brown wrote:
> > I do think that this is a big part of the issue, the patches have been
> > floating around for ages and it's not clear when they'll manage to make
> > it in (and hence when it'll be worth moving to use them).
> Maybe because nobody is actively promoting them and pushing them
> forward? It is not sufficient to just post patches to a mailing list
> and wait.
Yeah, it's a chicken and egg situation - it seems very difficult for
them to get integrated so few people are spending much time on them
which means it's not obvious that there's a pressing need for them :(
-------------- 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/20120125/3677c32e/attachment.sig>
next prev parent reply other threads:[~2012-01-25 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 1:54 Common clock API for i.MX Matt Sealey
2012-01-25 8:45 ` Russell King - ARM Linux
2012-01-25 13:45 ` Matt Sealey
2012-01-25 14:44 ` Russell King - ARM Linux
2012-01-25 20:33 ` Sylwester Nawrocki
2012-01-25 20:33 ` Sylwester Nawrocki
2012-01-25 14:53 ` Mark Brown
2012-01-25 15:42 ` Nicolas Pitre
2012-01-25 15:52 ` Mark Brown [this message]
2012-01-26 6:20 ` Shawn Guo
2012-01-26 19:02 ` Sascha Hauer
2012-02-07 0:20 ` Saravana Kannan
2012-01-26 6:10 ` Shawn Guo
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=20120125155202.GQ3687@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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.