Hello Greg,
I was just about to submit a patch fixing this issue. Should arrive in a
few minutes. Sorry.
Will this be the follow-on patch you mentioned for fixing the "sparse
errors" this driver produced? I'm wasn't sure what you meant with that.
Oddly enough, I failed to repeat the compilation issue with allmodconfig
on x86_64, but it did appear on allyesconfig. The problem is obvious,
and it's strange my own test compilations went through even so.
Regards,
Eli
On 27/07/13 00:03, Greg KH wrote:
On Fri, Jul 26, 2013 at 04:02:54PM +1000, Stephen Rothwell wrote:
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/staging/xillybus/xillybus_pcie.o:(.data+0x6d8): multiple definition of `xillyname'
drivers/staging/xillybus/xillybus_core.o:(.data+0x888): first defined here
Caused by commit 48bae0507410 ("staging: New driver: Xillybus generic
interface for FPGA").
I have disabled that driver.
I think I need to just always make any new staging driver only build as
a module, and not allowed to be built into the kernel. That will save
you time dealing with this, and me the extra time of marking them all as
modules-only every time :)
Sorry about this, I'll go fix this up now...
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
