linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build failure after merge of the clockevents tree
Date: Tue, 7 Jun 2016 13:12:54 +1000	[thread overview]
Message-ID: <20160607131254.55ec84d7@canb.auug.org.au> (raw)

Hi Daniel,

After merging the clockevents tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

drivers/clocksource/versatile.c: In function 'versatile_sched_clock_init':
drivers/clocksource/versatile.c:33:11: error: 'EXNIO' undeclared (first use in this function)
   return -EXNIO;
           ^
drivers/clocksource/versatile.c:33:11: note: each undeclared identifier is reported only once for each function it appears in
drivers/clocksource/versatile.c:33:10: warning: 'return' with a value, in function returning void
   return -EXNIO;
          ^
drivers/clocksource/versatile.c:39:9: warning: 'return' with a value, in function returning void
  return 0;
         ^
In file included from include/linux/clocksource.h:18:0,
                 from drivers/clocksource/versatile.c:14:
drivers/clocksource/versatile.c: At top level:
include/linux/of.h:1002:20: warning: comparison of distinct pointer types lacks a cast
        .data = (fn == (fn_type)NULL) ? fn : fn  }
                    ^
include/linux/of.h:1018:3: note: in expansion of macro '_OF_DECLARE'
   _OF_DECLARE(table, name, compat, fn, of_init_fn_1_ret)
   ^
include/linux/clocksource.h:247:2: note: in expansion of macro 'OF_DECLARE_1_RET'
  OF_DECLARE_1_RET(clksrc_ret, name, compat, fn)
  ^
drivers/clocksource/versatile.c:41:1: note: in expansion of macro 'CLOCKSOURCE_OF_DECLARE'
 CLOCKSOURCE_OF_DECLARE(vexpress, "arm,vexpress-sysreg",
 ^
include/linux/of.h:1002:20: warning: comparison of distinct pointer types lacks a cast
        .data = (fn == (fn_type)NULL) ? fn : fn  }
                    ^
include/linux/of.h:1018:3: note: in expansion of macro '_OF_DECLARE'
   _OF_DECLARE(table, name, compat, fn, of_init_fn_1_ret)
   ^
include/linux/clocksource.h:247:2: note: in expansion of macro 'OF_DECLARE_1_RET'
  OF_DECLARE_1_RET(clksrc_ret, name, compat, fn)
  ^
drivers/clocksource/versatile.c:43:1: note: in expansion of macro 'CLOCKSOURCE_OF_DECLARE'
 CLOCKSOURCE_OF_DECLARE(versatile, "arm,versatile-sysreg",
 ^

Caused by commit

  339ecd4051c3 ("clocksource/drivers/versatile: Convert init function to return error")

I have used the clockevents tree from next-20160606 for today.

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2016-06-07  3:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07  3:12 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-06-03  2:13 linux-next: build failure after merge of the clockevents tree Stephen Rothwell
2019-06-04  5:56 ` Daniel Lezcano
2019-06-04  6:02   ` Stephen Rothwell
2015-12-17  2:55 Stephen Rothwell
2014-05-26  6:07 Stephen Rothwell

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=20160607131254.55ec84d7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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).