linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff LaBundy <jeff@labundy.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	Mark Brown <broonie@kernel.org>
Subject: Re: linux-next: Tree for May 18 (input/misc/iqs269a.c & regmap)
Date: Mon, 18 May 2020 11:20:58 -0500	[thread overview]
Message-ID: <20200518162058.GA18713@labundy.com> (raw)
In-Reply-To: <60dadc36-daec-2c48-a317-843ce52ae4f5@infradead.org>

Hi Randy et al,

On Mon, May 18, 2020 at 08:42:43AM -0700, Randy Dunlap wrote:
> On 5/18/20 3:57 AM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20200515:
> > 
> 
> on i386:
> 
> 
> CONFIG_REGMAP_I2C=y
> CONFIG_I2C=m
> 
> WARNING: unmet direct dependencies detected for REGMAP_I2C
>   Depends on [m]: I2C [=m]
>   Selected by [y]:
>   - INPUT_IQS269A [=y] && !UML && INPUT [=y] && INPUT_MISC [=y]
> 
> 
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_smbus_byte_reg_read':
> regmap-i2c.c:(.text+0x192): undefined reference to `i2c_smbus_read_byte_data'
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_smbus_byte_reg_write':
> regmap-i2c.c:(.text+0x1d7): undefined reference to `i2c_smbus_write_byte_data'
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_smbus_word_reg_read':
> regmap-i2c.c:(.text+0x202): undefined reference to `i2c_smbus_read_word_data'
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_smbus_word_read_swapped':
> regmap-i2c.c:(.text+0x242): undefined reference to `i2c_smbus_read_word_data'
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_smbus_word_write_swapped':
> regmap-i2c.c:(.text+0x2a1): undefined reference to `i2c_smbus_write_word_data'
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_smbus_word_reg_write':
> regmap-i2c.c:(.text+0x2d7): undefined reference to `i2c_smbus_write_word_data'
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_i2c_smbus_i2c_read_reg16':
> regmap-i2c.c:(.text+0x310): undefined reference to `i2c_smbus_write_byte_data'
> ld: regmap-i2c.c:(.text+0x323): undefined reference to `i2c_smbus_read_byte'
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_i2c_smbus_i2c_write_reg16':
> regmap-i2c.c:(.text+0x39c): undefined reference to `i2c_smbus_write_i2c_block_data'
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_i2c_smbus_i2c_write':
> regmap-i2c.c:(.text+0x3db): undefined reference to `i2c_smbus_write_i2c_block_data'
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_i2c_smbus_i2c_read':
> regmap-i2c.c:(.text+0x427): undefined reference to `i2c_smbus_read_i2c_block_data'
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_i2c_read':
> regmap-i2c.c:(.text+0x49f): undefined reference to `i2c_transfer'
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_i2c_gather_write':
> regmap-i2c.c:(.text+0x524): undefined reference to `i2c_transfer'
> ld: drivers/base/regmap/regmap-i2c.o: in function `regmap_i2c_write':
> regmap-i2c.c:(.text+0x56c): undefined reference to `i2c_transfer_buffer_flags'
> ld: drivers/input/misc/iqs269a.o: in function `iqs269_i2c_driver_init':
> iqs269a.c:(.init.text+0xb): undefined reference to `i2c_register_driver'
> ld: drivers/input/misc/iqs269a.o: in function `iqs269_i2c_driver_exit':
> iqs269a.c:(.exit.text+0x9): undefined reference to `i2c_del_driver'
> 
> 
> 
> Full randconfig file is attached.

A complete oversight on my part; during my testing I did not realize
another module was selecting I2C for me. Valuable lesson learned :)

The kbuild test robot set off the alarm bells earlier today and I've
sent a patch [1] already. Many apologies for all of the noise.

> 
> -- 
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@infradead.org>

[1] https://patchwork.kernel.org/patch/11555469/

Kind regards,
Jeff LaBundy

       reply	other threads:[~2020-05-18 16:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200518205725.72eb3148@canb.auug.org.au>
     [not found] ` <60dadc36-daec-2c48-a317-843ce52ae4f5@infradead.org>
2020-05-18 16:20   ` Jeff LaBundy [this message]
2020-05-22 18:22     ` linux-next: Tree for May 18 (input/misc/iqs269a.c & regmap) Randy Dunlap
2020-05-22 21:49       ` Dmitry Torokhov

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=20200518162058.GA18713@labundy.com \
    --to=jeff@labundy.com \
    --cc=broonie@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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).