From: kbuild test robot <lkp@intel.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH] reset: remove unused device pointer from struct reset_control
Date: Wed, 18 Nov 2015 21:54:40 +0800 [thread overview]
Message-ID: <201511182131.td3crVmi%fengguang.wu@intel.com> (raw)
In-Reply-To: <1447854023-30152-1-git-send-email-p.zabel@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2650 bytes --]
Hi Philipp,
[auto build test WARNING on: v4.4-rc1]
[also build test WARNING on: next-20151118]
url: https://github.com/0day-ci/linux/commits/Philipp-Zabel/reset-remove-unused-device-pointer-from-struct-reset_control/20151118-214443
config: x86_64-randconfig-x012-11181928 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
drivers/reset/core.c: In function 'reset_control_get':
>> drivers/reset/core.c:217:24: warning: unused variable 'rstc' [-Wunused-variable]
struct reset_control *rstc;
^
vim +/rstc +217 drivers/reset/core.c
61fc4131 Philipp Zabel 2012-11-19 201
61fc4131 Philipp Zabel 2012-11-19 202 return rstc;
61fc4131 Philipp Zabel 2012-11-19 203 }
fc0a5921 Maxime Ripard 2013-12-20 204 EXPORT_SYMBOL_GPL(of_reset_control_get);
fc0a5921 Maxime Ripard 2013-12-20 205
fc0a5921 Maxime Ripard 2013-12-20 206 /**
fc0a5921 Maxime Ripard 2013-12-20 207 * reset_control_get - Lookup and obtain a reference to a reset controller.
fc0a5921 Maxime Ripard 2013-12-20 208 * @dev: device to be reset by the controller
fc0a5921 Maxime Ripard 2013-12-20 209 * @id: reset line name
fc0a5921 Maxime Ripard 2013-12-20 210 *
fc0a5921 Maxime Ripard 2013-12-20 211 * Returns a struct reset_control or IS_ERR() condition containing errno.
fc0a5921 Maxime Ripard 2013-12-20 212 *
fc0a5921 Maxime Ripard 2013-12-20 213 * Use of id names is optional.
fc0a5921 Maxime Ripard 2013-12-20 214 */
fc0a5921 Maxime Ripard 2013-12-20 215 struct reset_control *reset_control_get(struct device *dev, const char *id)
fc0a5921 Maxime Ripard 2013-12-20 216 {
fc0a5921 Maxime Ripard 2013-12-20 @217 struct reset_control *rstc;
fc0a5921 Maxime Ripard 2013-12-20 218
fc0a5921 Maxime Ripard 2013-12-20 219 if (!dev)
fc0a5921 Maxime Ripard 2013-12-20 220 return ERR_PTR(-EINVAL);
fc0a5921 Maxime Ripard 2013-12-20 221
5d79cb8b Philipp Zabel 2015-11-18 222 return of_reset_control_get(dev->of_node, id);
fc0a5921 Maxime Ripard 2013-12-20 223 }
61fc4131 Philipp Zabel 2012-11-19 224 EXPORT_SYMBOL_GPL(reset_control_get);
61fc4131 Philipp Zabel 2012-11-19 225
:::::: The code at line 217 was first introduced by commit
:::::: fc0a5921561c71be2c334a335c1680f7930434d7 reset: Add of_reset_control_get
:::::: TO: Maxime Ripard <maxime.ripard@free-electrons.com>
:::::: CC: Philipp Zabel <p.zabel@pengutronix.de>
---
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: 28235 bytes --]
prev parent reply other threads:[~2015-11-18 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 13:40 Philipp Zabel
2015-11-18 13:54 ` kbuild test robot [this message]
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=201511182131.td3crVmi%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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®