All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: 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 sunxi tree
Date: Fri, 5 Feb 2016 10:10:04 +0100	[thread overview]
Message-ID: <20160205091004.GC1139@lukather> (raw)
In-Reply-To: <20160205101412.56e4631b@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]

Hi Stephen,

On Fri, Feb 05, 2016 at 10:14:12AM +1100, Stephen Rothwell wrote:
> Hi Maxime,
> 
> After merging the sunxi tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> drivers/clk/sunxi/clk-sunxi.c: In function 'sunxi_mux_clk_setup':
> drivers/clk/sunxi/clk-sunxi.c:712:2: warning: 'return' with no value, in function returning non-void [-Wreturn-type]
>   return;
>   ^
> drivers/clk/sunxi/clk-sunxi.c:718:20: error: invalid storage class for function 'sun4i_cpu_clk_setup'
>  static void __init sun4i_cpu_clk_setup(struct device_node *node)
>                     ^
> drivers/clk/sunxi/clk-sunxi.c:718:1: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement]
>  static void __init sun4i_cpu_clk_setup(struct device_node *node)
>  ^
> In file included from include/linux/clk-provider.h:15:0,
>                  from drivers/clk/sunxi/clk-sunxi.c:18:
> include/linux/of.h:937:16: error: initializer element is not constant
>         .data = (fn == (fn_type)NULL) ? fn : fn  }
>                 ^
> include/linux/of.h:950:3: note: in expansion of macro '_OF_DECLARE'
>    _OF_DECLARE(table, name, compat, fn, of_init_fn_1)
>    ^
> 
> and on and on ...
> 
> Caused by commit
> 
>   1190461d5ad8 ("clk: sunxi: Remove clk_register_clkdev calls")
> 
> I have used the sunxi tree from next-20160204 for today.

It was a flacky merge on my side, sorry for that.

It's fixed and pushed, hopefully it won't break in the next version.

Thanks!
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-02-05  9:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 23:14 linux-next: build failure after merge of the sunxi tree Stephen Rothwell
2016-02-05  9:10 ` Maxime Ripard [this message]
2016-10-25  0:26 Stephen Rothwell
2016-10-25 10:41 ` Maxime Ripard
2017-03-07  0:10 Stephen Rothwell
2017-03-07  0:10 ` Stephen Rothwell
2017-03-07 21:39 ` Maxime Ripard
2017-03-07 21:39   ` Maxime Ripard
2017-03-08  8:26   ` Jani Nikula
2017-03-08  8:26     ` Jani Nikula
2017-03-08  9:49     ` Daniel Vetter
2017-03-08  9:49       ` Daniel Vetter
2017-10-31 20:43 Stephen Rothwell
2017-11-01  7:57 ` Corentin Labbe
2018-03-07 22:35 Stephen Rothwell
2018-03-08  2:37 ` Emmanuel Vadot
2018-03-08  3:19   ` Chen-Yu Tsai
2018-06-27 22:42 Stephen Rothwell
2020-01-06 22:20 Stephen Rothwell
2020-01-06 22:27 ` Maxime Ripard
2020-10-26 23:42 Stephen Rothwell
2020-10-27 15:28 ` Maxime Ripard
2021-11-22 23:27 Stephen Rothwell
2021-11-23  9:31 ` Maxime Ripard

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=20160205091004.GC1139@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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.