From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] clk for next
Date: Mon, 7 May 2012 10:24:59 +0100 [thread overview]
Message-ID: <20120507092458.GC4415@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAJOA=zPbq+uBwGgE5qWumtNZFhwgHNVPXhRr6Hfwe5QMjoZVQg@mail.gmail.com>
On Sun, May 06, 2012 at 07:20:18PM -0700, Turquette, Mike wrote:
> On Fri, May 4, 2012 at 10:45 AM, Mark Brown
> > On Fri, May 04, 2012 at 07:05:33PM +0200, Sascha Hauer wrote:
> > I'd also like to get the wm831x driver in there, I've not been looking
> > at it since it doesn't seem sensible to put the effort in until we've
> > got stuff flowing into -next.
> One thing to think about is the fact that CONFIG_COMMON_CLK pulls in
> clkdev. x86 doesn't have an arch/x86/include/asm/clkdev.h last time I
> looked.
Everything seemed to manage to build happily enough when I was testing,
this is how I was build testing, though I'm not immediately sure why
looking again. This does seem like we're stuck in the same failure that
we're in with gpiolib, and obviously the -next issues get in the way too :(
-------------- 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/20120507/156ac6ac/attachment.sig>
next prev parent reply other threads:[~2012-05-07 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 17:05 [GIT PULL] clk for next Sascha Hauer
2012-05-04 17:45 ` Mark Brown
2012-05-07 2:20 ` Turquette, Mike
2012-05-07 9:24 ` Mark Brown [this message]
2012-05-05 6:10 ` Shawn Guo
2012-05-05 9:23 ` Shawn Guo
2012-05-06 23:44 ` Turquette, Mike
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=20120507092458.GC4415@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 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).