From: kbuild test robot <lkp@intel.com>
To: Huibin Hong <huibin.hong@rock-chips.com>
Cc: kbuild-all@01.org, linux@roeck-us.net, huangtao@rock-chips.com,
Huibin Hong <huibin.hong@rock-chips.com>,
Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] watchdog: dw_wdt: fix overflow issue in dw_wdt_top_in_seconds
Date: Thu, 17 Aug 2017 04:24:16 +0800 [thread overview]
Message-ID: <201708170427.OwBklR08%fengguang.wu@intel.com> (raw)
In-Reply-To: <1502765113-1025-1-git-send-email-huibin.hong@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]
Hi Huibin,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.13-rc5 next-20170816]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Huibin-Hong/watchdog-dw_wdt-fix-overflow-issue-in-dw_wdt_top_in_seconds/20170817-033555
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All error/warnings (new ones prefixed by >>):
drivers//watchdog/dw_wdt.c: In function 'dw_wdt_top_in_seconds':
>> drivers//watchdog/dw_wdt.c:77:38: error: request for member 'clk' in something not a structure or union
return (cycles / clk_get_rate(dw_wdt.clk));
^
>> drivers//watchdog/dw_wdt.c:78:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
vim +/clk +77 drivers//watchdog/dw_wdt.c
68
69 static inline int dw_wdt_top_in_seconds(struct dw_wdt *dw_wdt, unsigned top)
70 {
71 /*
72 * There are 16 possible timeout values in 0..15 where the number of
73 * cycles is 2 ^ (16 + i) and the watchdog counts down.
74 */
75 unsigned int cycles = 1 << (16 + top);
76
> 77 return (cycles / clk_get_rate(dw_wdt.clk));
> 78 }
79
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 50926 bytes --]
next prev parent reply other threads:[~2017-08-16 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 2:45 Huibin Hong
2017-08-15 4:49 ` Guenter Roeck
2017-08-16 20:24 ` kbuild test robot [this message]
2017-08-16 20:30 ` kbuild test robot
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=201708170427.OwBklR08%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=huangtao@rock-chips.com \
--cc=huibin.hong@rock-chips.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@iguana.be \
/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®