All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette@linaro.org>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the clk tree
Date: Mon, 15 Apr 2013 17:42:36 -0700	[thread overview]
Message-ID: <20130416004236.6507.63400@quantum> (raw)
In-Reply-To: <516BA63B.5090707@gmail.com>

Quoting Sebastian Hesselbarth (2013-04-15 00:03:23)
> On 04/15/2013 07:04 AM, Stephen Rothwell wrote:
> > After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
> > failed like this:
> >
> > ERROR: "of_clk_add_provider" [drivers/clk/clk-si5351.ko] undefined!
> > ERROR: "of_clk_src_onecell_get" [drivers/clk/clk-si5351.ko] undefined!
> 
> Stephen,
> 
> I must have missed the both above when allowing clk-si5351 to be built
> for !OF. I sent a patch to make clk-si5351 depend on CONFIG_OF until
> we sort it out.
> 
> > ERROR: "__clk_get_flags" [drivers/clk/clk-si5351.ko] undefined!
> 
> I sent a patch to export the above function but Mike must have missed
> it. I resent it on list.
> 

Sorry about missing that export.

I've taken both of your fixes into clk-next.

Regards,
Mike

> Sebastian
> 
> > Caused by commit 9abd5f0555df ("clk: add si5351 i2c common clock
> > driver").  It probbaly need to depend on CONFIG_OF.
> >
> > I have used the clk tree from next-20130412 for today.

  reply	other threads:[~2013-04-16  0:43 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15  5:04 linux-next: build failure after merge of the clk tree Stephen Rothwell
2013-04-15  7:03 ` Sebastian Hesselbarth
2013-04-16  0:42   ` Mike Turquette [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-29  3:32 Stephen Rothwell
2014-01-29 10:02 ` Sebastian Hesselbarth
2014-12-16  3:45 Stephen Rothwell
     [not found] ` <20141216072034.29014.12434@quantum>
2014-12-17  3:47   ` Stephen Rothwell
2015-02-26  2:14 Stephen Rothwell
2015-02-26  9:09 ` Krzysztof Kozlowski
2015-02-27  0:01   ` Mike Turquette
2015-02-27  0:06     ` Stephen Rothwell
2015-02-27  0:06       ` Stephen Rothwell
2015-02-27  3:08 Stephen Rothwell
2015-02-27 17:42 ` Stephen Boyd
2015-03-04  9:56   ` Geert Uytterhoeven
2015-03-05  0:15     ` Mike Turquette
2015-07-27  4:11 Stephen Rothwell
2015-08-03 10:08 ` Tony Lindgren
2015-08-07 23:56   ` Stephen Boyd
2015-08-13 11:04 ` Olof Johansson
2015-08-12  7:19 Stephen Rothwell
2015-08-12  7:45 ` Geert Uytterhoeven
2015-08-12  8:23   ` Stephen Boyd
2015-08-12  8:03 ` Stephen Boyd
2017-06-05  0:14 Stephen Rothwell
2017-12-10 23:16 Stephen Rothwell
2017-12-14  0:57 ` Stephen Boyd
2018-01-01 21:51 Stephen Rothwell
2018-01-02 19:58 ` Stephen Boyd
2018-11-29 22:03 Stephen Rothwell
2019-05-02 23:25 Stephen Rothwell
2019-05-03 15:55 ` Stephen Boyd
2019-07-02  0:01 Stephen Rothwell
2019-07-02  1:14 ` Stephen Rothwell
2019-07-02  2:03   ` Stephen Rothwell
2019-07-05  1:24     ` Stephen Rothwell
2019-07-12 17:53     ` Stephen Boyd
2020-01-07 21:47 Stephen Rothwell
2020-05-11  0:55 Stephen Rothwell
2020-05-13  3:20 ` Stephen Boyd
2020-05-13  3:28 ` Stephen Boyd
2023-04-02 23:59 Stephen Rothwell
2023-04-05  0:28 ` Stephen Rothwell
2024-01-03 23:04 Stephen Rothwell
2024-01-04  0:59 ` Stephen Boyd
2024-07-16  0:41 Stephen Rothwell
2024-07-16 18:26 ` 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=20130416004236.6507.63400@quantum \
    --to=mturquette@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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.