public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Jim Davis <jim.epost@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next <linux-next@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	jdelvare@suse.com, wsa@the-dreams.de, linux-i2c@vger.kernel.org,
	Matt Fleming <matt.fleming@intel.com>
Subject: Re: randconfig build error with next-20150812, in drivers/i2c/busses/i2c-i801.c
Date: Fri, 25 Sep 2015 09:36:10 +0200	[thread overview]
Message-ID: <20150925093610.64ed7f59@endymion.delvare> (raw)
In-Reply-To: <CA+r1ZhjyBKcWbNB3hkPxoEKatojYk9=VPqSurZHPk9nfNp_gSQ@mail.gmail.com>

On Wed, 12 Aug 2015 08:42:18 -0700, Jim Davis wrote:
> Building with the attached random configuration file,
> 
> drivers/built-in.o: In function `dmi_check_onboard_devices':
> i2c-i801.c:(.text+0x126b36): undefined reference to `i2c_new_device'
> drivers/built-in.o: In function `i801_remove':
> i2c-i801.c:(.text+0x126b86): undefined reference to `i2c_del_adapter'
> drivers/built-in.o: In function `i801_probe':
> i2c-i801.c:(.text+0x127d08): undefined reference to `i2c_add_adapter'
> i2c-i801.c:(.text+0x127d6e): undefined reference to `i2c_new_device'

Sorry for the late reply. The error is caused by the following
combination of options:

CONFIG_I2C=m
CONFIG_I2C_I801=y

I can reproduce it even with mainline now. This is caused by
CONFIG_ITCO_WDT=y, which selects CONFIG_I2C_I801=y without selecting
its dependencies (CONFIG_I2C.)

Thanks for reporting, I'll post a fix shortly.

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2015-09-25  7:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 15:42 randconfig build error with next-20150812, in drivers/i2c/busses/i2c-i801.c Jim Davis
2015-09-25  7:36 ` Jean Delvare [this message]
2015-09-25 13:37   ` Matt Fleming
2015-09-25 14:06     ` Jean Delvare

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=20150925093610.64ed7f59@endymion.delvare \
    --to=jdelvare@suse.de \
    --cc=jdelvare@suse.com \
    --cc=jim.epost@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=wsa@the-dreams.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