From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Vivek Gautam <vivek.gautam@codeaurora.org>,
Jon Hunter <jonathanh@nvidia.com>,
Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thierry Reding <treding@nvidia.com>,
linux-tegra@vger.kernel.org, linux-usb@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH v6 1/4] reset: Add APIs to manage array of resets
Date: Tue, 20 Jun 2017 04:21:55 +0800 [thread overview]
Message-ID: <201706200445.RVcRobQj%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170619143408.15668-2-p.zabel@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2863 bytes --]
Hi Vivek,
[auto build test WARNING on pza/reset/next]
[also build test WARNING on v4.12-rc6 next-20170619]
[cannot apply to balbi-usb/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/Philipp-Zabel/reset-Add-APIs-to-manage-array-of-resets/20170620-021320
base: git://git.pengutronix.de/git/pza/linux reset/next
config: i386-randconfig-c0-06200218 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
In file included from drivers/gpu//drm/nouveau/include/nvif/os.h:28:0,
from drivers/gpu//drm/nouveau/include/nvkm/core/os.h:3,
from drivers/gpu//drm/nouveau/include/nvkm/core/event.h:3,
from drivers/gpu//drm/nouveau/include/nvkm/core/device.h:3,
from drivers/gpu//drm/nouveau/include/nvkm/core/subdev.h:3,
from drivers/gpu//drm/nouveau/include/nvkm/core/engine.h:4,
from drivers/gpu//drm/nouveau/include/nvkm/engine/fifo.h:3,
from drivers/gpu//drm/nouveau/nvkm/engine/fifo/priv.h:4,
from drivers/gpu//drm/nouveau/nvkm/engine/fifo/chan.h:4,
from drivers/gpu//drm/nouveau/nvkm/engine/fifo/channv50.h:4,
from drivers/gpu//drm/nouveau/nvkm/engine/fifo/chang84.c:24:
>> include/linux/reset.h:110:37: warning: 'struct reset_control_array' declared inside parameter list
void reset_control_array_put(struct reset_control_array *resets)
^
>> include/linux/reset.h:110:37: warning: its scope is only this definition or declaration, which is probably not what you want
vim +110 include/linux/reset.h
94 return optional ? NULL : ERR_PTR(-ENOTSUPP);
95 }
96
97 static inline struct reset_control *
98 devm_reset_control_array_get(struct device *dev, bool shared, bool optional)
99 {
100 return optional ? NULL : ERR_PTR(-ENOTSUPP);
101 }
102
103 static inline struct reset_control *
104 of_reset_control_array_get(struct device_node *np, bool shared, bool optional)
105 {
106 return optional ? NULL : ERR_PTR(-ENOTSUPP);
107 }
108
109 static inline
> 110 void reset_control_array_put(struct reset_control_array *resets)
111 {
112 }
113
114 #endif /* CONFIG_RESET_CONTROLLER */
115
116 /**
117 * reset_control_get_exclusive - Lookup and obtain an exclusive reference
118 * to a reset controller.
---
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: 25302 bytes --]
next prev parent reply other threads:[~2017-06-19 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 14:34 [PATCH v6 0/4] reset: APIs to manage a list of resets Philipp Zabel
2017-06-19 14:34 ` [PATCH v6 1/4] reset: Add APIs to manage array " Philipp Zabel
2017-06-19 19:42 ` kbuild test robot
2017-06-19 20:21 ` kbuild test robot [this message]
2017-06-20 7:02 ` Philipp Zabel
[not found] ` <20170619143408.15668-1-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-06-19 14:34 ` [PATCH v6 2/4] usb: dwc3: of-simple: Re-order resource handling in remove Philipp Zabel
2017-06-19 14:34 ` [PATCH v6 3/4] usb: dwc3: of-simple: Add support to get resets for the device Philipp Zabel
2017-06-19 14:34 ` [PATCH v6 4/4] soc/tegra: pmc: Use the new reset APIs to manage reset controllers Philipp Zabel
[not found] ` <20170619143408.15668-5-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2018-02-13 13:54 ` Jon Hunter
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=201706200445.RVcRobQj%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-msm@vger.kernel.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=treding@nvidia.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