From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: devres: introduce managed enable and disable operations
Date: Sun, 12 Feb 2017 18:34:04 -0800 [thread overview]
Message-ID: <20170213023404.GA27642@dtor-ws> (raw)
In-Reply-To: <201702130901.hihQazwR%fengguang.wu@intel.com>
On Mon, Feb 13, 2017 at 10:00:14AM +0800, kbuild test robot wrote:
> Hi Dmitry,
>
> [auto build test ERROR on regulator/for-next]
> [cannot apply to v4.10-rc8]
> [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/Dmitry-Torokhov/regulator-devres-introduce-managed-enable-and-disable-operations/20170213-085344
> base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
> config: x86_64-randconfig-n0-02130915 (attached as .config)
> compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> drivers/gpu/drm/bridge/analogix-anx78xx.c: In function 'anx78xx_poweroff':
> >> drivers/gpu/drm/bridge/analogix-anx78xx.c:664:3: error: implicit declaration of function 'regulator_disable' [-Werror=implicit-function-declaration]
> err = regulator_disable(pdata->dvdd10);
> ^
> cc1: some warnings being treated as errors
So I lost stub for regulator_disable(), V2 of the patch sent.
Thanks.
--
Dmitry
prev parent reply other threads:[~2017-02-13 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 0:48 [PATCH] regulator: devres: introduce managed enable and disable operations Dmitry Torokhov
2017-02-13 2:00 ` kbuild test robot
2017-02-13 2:34 ` Dmitry Torokhov [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=20170213023404.GA27642@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=broonie@kernel.org \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkp@intel.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