All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	grant.likely@linaro.org, Linus Walleij <linus.walleij@linaro.org>
Subject: Re: linux-next: Tree for May 8 (gpio-mcp23s08)
Date: Wed, 08 May 2013 10:57:27 -0700	[thread overview]
Message-ID: <518A9207.5030309@infradead.org> (raw)
In-Reply-To: <20130508140122.e4747b58be4333060b7a248a@canb.auug.org.au>

On 05/07/13 21:01, Stephen Rothwell wrote:
> Hi all,
> 
> Please do not add any v3.11 destined work to your linux-next included
> branches until after v3.10-rc1 is released.
> 
> I am receiving a (un)reasonable number of conflicts from there being
> multiple copies of some commits in various trees.   Please clean this up
> and resist the temptataion to rebase your trees on the way to your
> upstream ...
> 
> Changes since 20130506:
> 
> <crickets :-)>
> 


on i386:

drivers/built-in.o: In function `mcp23017_write':
gpio-mcp23s08.c:(.text+0x20e9): undefined reference to `i2c_smbus_write_word_data'
drivers/built-in.o: In function `mcp23017_read':
gpio-mcp23s08.c:(.text+0x2103): undefined reference to `i2c_smbus_read_word_data'
drivers/built-in.o: In function `mcp23008_write':
gpio-mcp23s08.c:(.text+0x2164): undefined reference to `i2c_smbus_write_byte_data'
drivers/built-in.o: In function `mcp23008_read':
gpio-mcp23s08.c:(.text+0x217f): undefined reference to `i2c_smbus_read_byte_data'
drivers/built-in.o: In function `mcp23s08_init':
gpio-mcp23s08.c:(.init.text+0x1ae): undefined reference to `i2c_register_driver'
drivers/built-in.o: In function `mcp23s08_exit':
gpio-mcp23s08.c:(.exit.text+0x22): undefined reference to `i2c_del_driver'


when CONFIG_I2C=m and CONFIG_GPIO_MCP23S08=y.


-- 
~Randy

  reply	other threads:[~2013-05-08 17:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08  4:01 linux-next: Tree for May 8 Stephen Rothwell
2013-05-08  4:01 ` Stephen Rothwell
2013-05-08 17:57 ` Randy Dunlap [this message]
2013-05-08 18:04 ` linux-next: Tree for May 8 (dlm) Randy Dunlap
2013-05-08 18:04   ` [Cluster-devel] " Randy Dunlap
2013-05-08 23:47   ` Stephen Rothwell
2013-05-08 23:47     ` [Cluster-devel] " Stephen Rothwell
2013-05-09 16:50     ` David Teigland
2013-05-09 16:50       ` [Cluster-devel] " David Teigland
2013-05-09 17:08       ` Randy Dunlap
2013-05-09 17:08         ` [Cluster-devel] " Randy Dunlap
2013-05-13  9:18         ` Steven Whitehouse
2013-05-13  9:18           ` [Cluster-devel] " Steven Whitehouse
2013-05-13 16:30           ` Randy Dunlap
2013-05-13 16:30             ` [Cluster-devel] " Randy Dunlap
     [not found]             ` <51913F8B.7080201@infradead.org>
     [not found]               ` <51914045.1060900@infradead.org>
2013-05-13 19:45                 ` Randy Dunlap
2013-05-13 19:45                   ` [Cluster-devel] " Randy Dunlap
2013-05-14  8:51                   ` Steven Whitehouse
2013-05-14  8:51                     ` [Cluster-devel] " Steven Whitehouse
2013-05-14 17:02                     ` [PATCH -next] gfs2: fix DLM depends to fix build errors Randy Dunlap
2013-05-14 17:02                       ` [Cluster-devel] " Randy Dunlap
2013-05-15 10:05                       ` Steven Whitehouse
2013-05-15 10:05                         ` [Cluster-devel] " Steven Whitehouse
2013-05-08 18:26 ` [PATCH -next] media/usb: fix kconfig dependencies (aka bool depending on tristate considered harmful) Randy Dunlap
2013-05-08 21:18   ` Yann E. MORIN
2013-05-08 21:28     ` [PATCH -next v2] " Randy Dunlap

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=518A9207.5030309@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=grant.likely@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.