From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Michael Welling <mwelling@ieee.org>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, Tony Lindgren <tony@atomide.com>,
Pavel Machek <pavel@ucw.cz>, Felipe Balbi <balbi@ti.com>,
Sebastian Reichel <sre@kernel.org>, Roger Quadros <rogerq@ti.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH v2] Input: tsc2005 - Add support for tsc2004
Date: Tue, 27 Oct 2015 22:45:55 -0700 [thread overview]
Message-ID: <20151028054555.GB16963@localhost> (raw)
In-Reply-To: <20151028053831.GA10851@deathstar>
On Wed, Oct 28, 2015 at 12:38:31AM -0500, Michael Welling wrote:
> On Wed, Oct 28, 2015 at 12:37:35PM +0800, kbuild test robot wrote:
> > Hi Michael,
> >
> > [auto build test ERROR on input/next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
> >
> > url: https://github.com/0day-ci/linux/commits/Michael-Welling/Input-tsc2005-Add-support-for-tsc2004/20151028-082017
> > config: x86_64-randconfig-s1-10281141 (attached as .config)
> > reproduce:
> > # save the attached .config to linux build tree
> > make ARCH=x86_64
> >
> > All errors (new ones prefixed by >>):
> >
> > drivers/built-in.o: In function `tsc2005_cmd':
> > tsc2005.c:(.text+0x21a352): undefined reference to `i2c_smbus_write_byte'
> > drivers/built-in.o: In function `tsc200x_probe_common':
> > >> tsc2005.c:(.text+0x21b554): undefined reference to `__devm_regmap_init_i2c'
> > drivers/built-in.o: In function `tsc2005_modinit':
> > tsc2005.c:(.init.text+0xe2b2): undefined reference to `i2c_register_driver'
> > drivers/built-in.o: In function `tsc2005_exit':
> > tsc2005.c:(.exit.text+0xf4c): undefined reference to `i2c_del_driver'
> >
>
> Sorry Mr. Robot but this configuration does not make sense.
>
> How is CONFIG_REGMAP_I2C=m set without CONFIG_I2C being selected?
> CONFIG_REGMAP_I2C depends on CONFIG_I2C.
The call to devm_regmap_init_i2c() in tsc200x_probe_common() is not
protected by #ifdef guard and we do not have stub for it in case of
!CONFIG_I2C.
Thanks.
--
Dmitry
prev parent reply other threads:[~2015-10-28 5:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 20:36 [PATCH] Input: tsc2005 - Add support for tsc2004 Michael Welling
2015-10-27 20:49 ` Michael Welling
[not found] ` <1445978203-31264-1-git-send-email-mwelling-EkmVulN54Sk@public.gmane.org>
2015-10-27 23:34 ` kbuild test robot
2015-10-28 0:17 ` [PATCH v2] " Michael Welling
[not found] ` <1445991421-29938-1-git-send-email-mwelling-EkmVulN54Sk@public.gmane.org>
2015-10-28 1:51 ` Dmitry Torokhov
2015-10-28 5:23 ` Michael Welling
2015-10-28 5:41 ` Dmitry Torokhov
2015-10-28 5:48 ` Michael Welling
2015-10-28 6:12 ` Dmitry Torokhov
2015-10-30 12:59 ` Arnd Bergmann
2015-10-28 4:37 ` kbuild test robot
2015-10-28 5:38 ` Michael Welling
2015-10-28 5:45 ` 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=20151028054555.GB16963@localhost \
--to=dmitry.torokhov@gmail.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mwelling@ieee.org \
--cc=pavel@ucw.cz \
--cc=rogerq@ti.com \
--cc=sre@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).