From: Paul Bolle <pebolle@tiscali.nl>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: linux-clk@vger.kernel.org, sboyd@codeaurora.org,
mturquette@linaro.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3] Add TI CDCE925 I2C controlled clock synthesizer driver
Date: Tue, 02 Jun 2015 11:07:14 +0200 [thread overview]
Message-ID: <1433236034.2361.90.camel@x220> (raw)
In-Reply-To: <556D6CB4.30900@topic.nl>
On Tue, 2015-06-02 at 10:43 +0200, Mike Looijmans wrote:
> Out of curiousity, I did try a compile on the x86 host, but couldn't select
> the driver because it depends on CONFIG_OF, so I just compiled if for the ARM
> target to verify that it still compiles in kernel 4.1. How did you manage to
> compile the driver on the x86?
With this hack:
make drivers/clk/clk-cdce925.o
(I thought this is documented somewhere, but I can't actually find the
documentation. I guess it's just a feature of make.)
It bypasses much of the build infrastructure, but comes in handy when
you quickly want to know whether something can actually be build. Eg,
you see some code and wonder "how can this build?"
(Sometimes this requires setting CFLAGS on the make command line, or
adding things like CONFIG_WHATEVER=y to the command line to get sane
results, for some value of sane. By that time I usually give up.)
Downside is, of course, that you can build things outside of the
supported configurations. So it's best to state clearly that one built
something using this hack. I sinned against that rule, but apparently
got lucky, because this driver is not 32 bits only!
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-06-02 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 10:13 [PATCH v3] Add TI CDCE925 I2C controlled clock synthesizer driver Mike Looijmans
2015-06-02 7:50 ` Paul Bolle
2015-06-02 8:39 ` Mike Looijmans
2015-06-02 8:43 ` Mike Looijmans
2015-06-02 9:07 ` Paul Bolle [this message]
[not found] ` <1433153623-29205-1-git-send-email-mike.looijmans-Oq418RWZeHk@public.gmane.org>
2015-06-03 5:25 ` [PATCH v4] " Mike Looijmans
[not found] ` <1433309119-5186-1-git-send-email-mike.looijmans-Oq418RWZeHk@public.gmane.org>
2015-06-03 22:25 ` Michael Turquette
2015-06-03 22:30 ` Stephen Boyd
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=1433236034.2361.90.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
--cc=mturquette@linaro.org \
--cc=sboyd@codeaurora.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).