From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: Freescale fec.c driver breakage
Date: Mon, 4 Jun 2012 10:19:37 +0200 [thread overview]
Message-ID: <20120604081937.GH30400@pengutronix.de> (raw)
In-Reply-To: <4FCC3CB4.5030107@snapgear.com>
Hi Greg,
On Mon, Jun 04, 2012 at 02:42:28PM +1000, Greg Ungerer wrote:
>
> Hi Sascha,
>
> Commit f4d40de39a23f0c39cca55ac63e1175c69c3d2f7 ("net fec: do not
> depend on grouped clocks") breaks compilation of the FEC driver for
> non iMX platforms in linux-3.5-rc1. For example when compiling for
> ColdFire I get:
>
> LD vmlinux
> drivers/built-in.o: In function `fec_probe':
> fec.c:(.devinit.text+0x1e0): undefined reference to `devm_clk_get'
Sorry, I forgot that this driver is used on coldfire.
>
> Trivially we could conditionalize the code block that calls
> devm_clk_get() in the probe routine, but that is kind of ugly.
It's ugly, but the only other solution I see is that you could provide a
dummy devm_clk_get() for coldfire. Added Mark to Cc, maybe he has
another idea?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2012-06-04 8:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 4:42 Freescale fec.c driver breakage Greg Ungerer
2012-06-04 8:19 ` Sascha Hauer [this message]
2012-06-04 9:16 ` Mark Brown
2012-06-05 6:55 ` Greg Ungerer
2012-06-05 9:41 ` Mark Brown
2012-06-05 12:17 ` Greg Ungerer
2012-06-05 12:24 ` Mark Brown
2012-06-05 12:36 ` Greg Ungerer
2012-06-05 12:40 ` Mark Brown
2012-06-05 12:48 ` Sascha Hauer
2012-06-05 13:24 ` Greg Ungerer
2012-06-05 13:41 ` Mark Brown
2012-06-05 14:35 ` Steven King
2012-06-06 7:41 ` Greg Ungerer
2012-06-07 23:36 ` Mark Brown
2012-06-05 13:42 ` Sascha Hauer
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=20120604081937.GH30400@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).