From: kbuild test robot <lkp@intel.com>
To: Heiko Schocher <hs@denx.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Heiko Schocher <hs@denx.de>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Georg.Soffel@bosch-si.com, rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2] rtc: pcf8563: add CLKOUT to common clock framework
Date: Fri, 16 Oct 2015 18:22:32 +0800 [thread overview]
Message-ID: <201510161849.iHblv4Zq%fengguang.wu@intel.com> (raw)
In-Reply-To: <1444982369-26046-1-git-send-email-hs@denx.de>
[-- Attachment #1: Type: text/plain, Size: 9959 bytes --]
Hi Heiko,
[auto build test WARNING on abelloni/rtc-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
url: https://github.com/0day-ci/linux/commits/Heiko-Schocher/rtc-pcf8563-add-CLKOUT-to-common-clock-framework/20151016-160221
config: parisc-allyesconfig (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=parisc
All warnings (new ones prefixed by >>):
drivers/rtc/rtc-pcf8563.c:87:17: error: field 'clkout_hw' has incomplete type
struct clk_hw clkout_hw;
^
In file included from arch/parisc/include/asm/bug.h:4:0,
from include/linux/bug.h:4,
from include/linux/io.h:23,
from include/linux/clk-provider.h:14,
from drivers/rtc/rtc-pcf8563.c:17:
drivers/rtc/rtc-pcf8563.c: In function 'pcf8563_clkout_recalc_rate':
include/linux/kernel.h:811:48: warning: initialization from incompatible pointer type
const typeof( ((type *)0)->member ) *__mptr = (ptr); \
^
drivers/rtc/rtc-pcf8563.c:406:35: note: in expansion of macro 'container_of'
#define clkout_hw_to_pcf8563(_hw) container_of(_hw, struct pcf8563, clkout_hw)
^
drivers/rtc/rtc-pcf8563.c:418:28: note: in expansion of macro 'clkout_hw_to_pcf8563'
struct pcf8563 *pcf8563 = clkout_hw_to_pcf8563(hw);
^
>> include/linux/kernel.h:811:48: warning: (near initialization for 'pcf8563')
const typeof( ((type *)0)->member ) *__mptr = (ptr); \
^
drivers/rtc/rtc-pcf8563.c:406:35: note: in expansion of macro 'container_of'
#define clkout_hw_to_pcf8563(_hw) container_of(_hw, struct pcf8563, clkout_hw)
^
drivers/rtc/rtc-pcf8563.c:418:28: note: in expansion of macro 'clkout_hw_to_pcf8563'
struct pcf8563 *pcf8563 = clkout_hw_to_pcf8563(hw);
^
drivers/rtc/rtc-pcf8563.c: In function 'pcf8563_clkout_set_rate':
include/linux/kernel.h:811:48: warning: initialization from incompatible pointer type
const typeof( ((type *)0)->member ) *__mptr = (ptr); \
^
drivers/rtc/rtc-pcf8563.c:406:35: note: in expansion of macro 'container_of'
#define clkout_hw_to_pcf8563(_hw) container_of(_hw, struct pcf8563, clkout_hw)
^
drivers/rtc/rtc-pcf8563.c:445:28: note: in expansion of macro 'clkout_hw_to_pcf8563'
struct pcf8563 *pcf8563 = clkout_hw_to_pcf8563(hw);
^
>> include/linux/kernel.h:811:48: warning: (near initialization for 'pcf8563')
const typeof( ((type *)0)->member ) *__mptr = (ptr); \
^
drivers/rtc/rtc-pcf8563.c:406:35: note: in expansion of macro 'container_of'
#define clkout_hw_to_pcf8563(_hw) container_of(_hw, struct pcf8563, clkout_hw)
^
drivers/rtc/rtc-pcf8563.c:445:28: note: in expansion of macro 'clkout_hw_to_pcf8563'
struct pcf8563 *pcf8563 = clkout_hw_to_pcf8563(hw);
^
drivers/rtc/rtc-pcf8563.c: In function 'pcf8563_clkout_control':
include/linux/kernel.h:811:48: warning: initialization from incompatible pointer type
const typeof( ((type *)0)->member ) *__mptr = (ptr); \
^
drivers/rtc/rtc-pcf8563.c:406:35: note: in expansion of macro 'container_of'
#define clkout_hw_to_pcf8563(_hw) container_of(_hw, struct pcf8563, clkout_hw)
^
drivers/rtc/rtc-pcf8563.c:469:28: note: in expansion of macro 'clkout_hw_to_pcf8563'
struct pcf8563 *pcf8563 = clkout_hw_to_pcf8563(hw);
^
>> include/linux/kernel.h:811:48: warning: (near initialization for 'pcf8563')
const typeof( ((type *)0)->member ) *__mptr = (ptr); \
^
drivers/rtc/rtc-pcf8563.c:406:35: note: in expansion of macro 'container_of'
#define clkout_hw_to_pcf8563(_hw) container_of(_hw, struct pcf8563, clkout_hw)
^
drivers/rtc/rtc-pcf8563.c:469:28: note: in expansion of macro 'clkout_hw_to_pcf8563'
struct pcf8563 *pcf8563 = clkout_hw_to_pcf8563(hw);
^
drivers/rtc/rtc-pcf8563.c: In function 'pcf8563_clkout_is_prepared':
include/linux/kernel.h:811:48: warning: initialization from incompatible pointer type
const typeof( ((type *)0)->member ) *__mptr = (ptr); \
^
drivers/rtc/rtc-pcf8563.c:406:35: note: in expansion of macro 'container_of'
#define clkout_hw_to_pcf8563(_hw) container_of(_hw, struct pcf8563, clkout_hw)
^
drivers/rtc/rtc-pcf8563.c:498:28: note: in expansion of macro 'clkout_hw_to_pcf8563'
struct pcf8563 *pcf8563 = clkout_hw_to_pcf8563(hw);
^
>> include/linux/kernel.h:811:48: warning: (near initialization for 'pcf8563')
const typeof( ((type *)0)->member ) *__mptr = (ptr); \
^
drivers/rtc/rtc-pcf8563.c:406:35: note: in expansion of macro 'container_of'
#define clkout_hw_to_pcf8563(_hw) container_of(_hw, struct pcf8563, clkout_hw)
^
drivers/rtc/rtc-pcf8563.c:498:28: note: in expansion of macro 'clkout_hw_to_pcf8563'
struct pcf8563 *pcf8563 = clkout_hw_to_pcf8563(hw);
^
drivers/rtc/rtc-pcf8563.c: At top level:
drivers/rtc/rtc-pcf8563.c:509:21: error: variable 'pcf8563_clkout_ops' has initializer but incomplete type
static const struct clk_ops pcf8563_clkout_ops = {
^
drivers/rtc/rtc-pcf8563.c:510:2: error: unknown field 'prepare' specified in initializer
.prepare = pcf8563_clkout_prepare,
^
drivers/rtc/rtc-pcf8563.c:510:2: warning: excess elements in struct initializer
>> drivers/rtc/rtc-pcf8563.c:510:2: warning: (near initialization for 'pcf8563_clkout_ops')
drivers/rtc/rtc-pcf8563.c:511:2: error: unknown field 'unprepare' specified in initializer
.unprepare = pcf8563_clkout_unprepare,
^
drivers/rtc/rtc-pcf8563.c:511:2: warning: excess elements in struct initializer
drivers/rtc/rtc-pcf8563.c:511:2: warning: (near initialization for 'pcf8563_clkout_ops')
drivers/rtc/rtc-pcf8563.c:512:2: error: unknown field 'is_prepared' specified in initializer
.is_prepared = pcf8563_clkout_is_prepared,
^
drivers/rtc/rtc-pcf8563.c:512:2: warning: excess elements in struct initializer
drivers/rtc/rtc-pcf8563.c:512:2: warning: (near initialization for 'pcf8563_clkout_ops')
drivers/rtc/rtc-pcf8563.c:513:2: error: unknown field 'recalc_rate' specified in initializer
.recalc_rate = pcf8563_clkout_recalc_rate,
^
drivers/rtc/rtc-pcf8563.c:513:2: warning: excess elements in struct initializer
drivers/rtc/rtc-pcf8563.c:513:2: warning: (near initialization for 'pcf8563_clkout_ops')
drivers/rtc/rtc-pcf8563.c:514:2: error: unknown field 'round_rate' specified in initializer
.round_rate = pcf8563_clkout_round_rate,
^
drivers/rtc/rtc-pcf8563.c:514:2: warning: excess elements in struct initializer
drivers/rtc/rtc-pcf8563.c:514:2: warning: (near initialization for 'pcf8563_clkout_ops')
drivers/rtc/rtc-pcf8563.c:515:2: error: unknown field 'set_rate' specified in initializer
.set_rate = pcf8563_clkout_set_rate,
^
drivers/rtc/rtc-pcf8563.c:515:2: warning: excess elements in struct initializer
drivers/rtc/rtc-pcf8563.c:515:2: warning: (near initialization for 'pcf8563_clkout_ops')
drivers/rtc/rtc-pcf8563.c: In function 'pcf8563_clkout_register_clk':
drivers/rtc/rtc-pcf8563.c:523:23: error: storage size of 'init' isn't known
struct clk_init_data init;
^
drivers/rtc/rtc-pcf8563.c:535:15: error: 'CLK_IS_ROOT' undeclared (first use in this function)
init.flags = CLK_IS_ROOT;
^
drivers/rtc/rtc-pcf8563.c:535:15: note: each undeclared identifier is reported only once for each function it appears in
drivers/rtc/rtc-pcf8563.c:544:2: error: implicit declaration of function 'clk_register' [-Werror=implicit-function-declaration]
clk = clk_register(&client->dev, &pcf8563->clkout_hw);
^
drivers/rtc/rtc-pcf8563.c:547:3: error: implicit declaration of function 'of_clk_add_provider' [-Werror=implicit-function-declaration]
of_clk_add_provider(node, of_clk_src_simple_get, clk);
^
drivers/rtc/rtc-pcf8563.c:547:29: error: 'of_clk_src_simple_get' undeclared (first use in this function)
of_clk_add_provider(node, of_clk_src_simple_get, clk);
^
drivers/rtc/rtc-pcf8563.c:523:23: warning: unused variable 'init' [-Wunused-variable]
struct clk_init_data init;
^
cc1: some warnings being treated as errors
vim +/pcf8563_clkout_ops +510 drivers/rtc/rtc-pcf8563.c
503 if (ret < 0)
504 return ret;
505
506 return !!(buf & PCF8563_REG_CLKO_FE);
507 }
508
> 509 static const struct clk_ops pcf8563_clkout_ops = {
> 510 .prepare = pcf8563_clkout_prepare,
511 .unprepare = pcf8563_clkout_unprepare,
512 .is_prepared = pcf8563_clkout_is_prepared,
513 .recalc_rate = pcf8563_clkout_recalc_rate,
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 42281 bytes --]
next prev parent reply other threads:[~2015-10-16 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 7:59 Heiko Schocher
2015-10-16 10:22 ` kbuild test robot [this message]
2015-10-16 10:46 ` kbuild test robot
2015-10-16 10:54 ` Alexandre Belloni
2015-10-16 11:00 ` Alexandre Belloni
2015-10-16 11:31 ` Heiko Schocher
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=201510161849.iHblv4Zq%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Georg.Soffel@bosch-si.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=hs@denx.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
/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
all inboxes | Powered by JetHome®