From: kbuild test robot <lkp@intel.com>
To: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-usb@vger.kernel.org,
p.zabel@pengutronix.de, swarren@wwwdotorg.org,
thierry.reding@gmail.com, balbi@kernel.org,
Vivek Gautam <vivek.gautam@codeaurora.org>
Subject: Re: [PATCH v2 1/4] reset: Add API to count number of reset available with device
Date: Tue, 4 Apr 2017 12:22:16 +0800 [thread overview]
Message-ID: <201704041234.RGKT8Ime%fengguang.wu@intel.com> (raw)
In-Reply-To: <1491226922-20307-2-git-send-email-vivek.gautam@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Hi Vivek,
[auto build test ERROR on balbi-usb/next]
[also build test ERROR on v4.11-rc5 next-20170403]
[cannot apply to pza/reset/next]
[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/Vivek-Gautam/reset-APIs-to-manage-a-list-of-resets/20170404-111639
base: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git next
config: i386-randconfig-r0-201714 (attached as .config)
compiler: gcc-5 (Debian 5.4.1-2) 5.4.1 20160904
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from drivers/usb/dwc2/platform.c:48:0:
>> include/linux/reset.h:84:1: error: expected identifier or '(' before '{' token
{
^
include/linux/reset.h:83:19: warning: 'of_reset_control_get_count' declared 'static' but never defined [-Wunused-function]
static inline int of_reset_control_get_count(struct device_node *node);
^
vim +84 include/linux/reset.h
78 int index, bool shared, bool optional)
79 {
80 return optional ? NULL : ERR_PTR(-ENOTSUPP);
81 }
82
83 static inline int of_reset_control_get_count(struct device_node *node);
> 84 {
85 return -ENOTSUPP;
86 }
87
---
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: 29765 bytes --]
next prev parent reply other threads:[~2017-04-04 4:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 13:41 [PATCH v2 0/4] reset: APIs to manage a list of resets Vivek Gautam
2017-04-03 13:41 ` [PATCH v2 1/4] reset: Add API to count number of reset available with device Vivek Gautam
2017-04-04 4:22 ` kbuild test robot [this message]
2017-04-03 13:42 ` [PATCH v2 2/4] reset: Add APIs to manage array of resets Vivek Gautam
2017-04-03 16:36 ` Philipp Zabel
2017-04-04 10:39 ` Vivek Gautam
2017-04-04 12:47 ` Philipp Zabel
2017-04-05 6:50 ` Vivek Gautam
2017-04-04 4:12 ` kbuild test robot
2017-04-04 4:14 ` kbuild test robot
2017-04-04 4:23 ` Vivek Gautam
2017-04-03 13:42 ` [PATCH v2 3/4] usb: dwc3: of-simple: Add support to get resets for the device Vivek Gautam
2017-04-04 5:20 ` [PATCH] usb: dwc3: of-simple: fix noderef.cocci warnings kbuild test robot
2017-04-04 5:20 ` [PATCH v2 3/4] usb: dwc3: of-simple: Add support to get resets for the device kbuild test robot
2017-04-04 5:34 ` kbuild test robot
2017-04-03 13:42 ` [PATCH v2 4/4] soc/tegra: pmc: Use the new reset APIs to manage reset controllers Vivek Gautam
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=201704041234.RGKT8Ime%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=balbi@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=vivek.gautam@codeaurora.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
all inboxes | Powered by JetHome®