linux-kernel - Re: linux-next: build failure after merge of the spi tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <521C532B.7030009@ti.com>
Date:	Tue, 27 Aug 2013 12:50:11 +0530
From:	Sourav Poddar <sourav.poddar@...com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Mark Brown <broonie@...nel.org>, <linux-next@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the spi tree

Hi,
On Tuesday 27 August 2013 11:45 AM, Stephen Rothwell wrote:
> Hi Mark,
>
> After merging the spi tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> In file included from drivers/spi/spi-ti-qspi.c:19:0:
> include/linux/module.h:87:32: error: '__mod_of_device_table' aliased to undefined symbol 'dra7xxx_qspi_match'
>   extern const struct gtype##_id __mod_##gtype##_table  \
>                                  ^
> include/linux/module.h:145:3: note: in expansion of macro 'MODULE_GENERIC_TABLE'
>     MODULE_GENERIC_TABLE(type##_device,name)
>     ^
> drivers/spi/spi-ti-qspi.c:458:1: note: in expansion of macro 'MODULE_DEVICE_TABLE'
>   MODULE_DEVICE_TABLE(of, dra7xxx_qspi_match);
>   ^
>
> Caused by commit 505a14954e2d ("spi/qspi: Add qspi flash controller").
>
> Clearly not build tested as a module. :-(
Yes, module build test was missed.  I will send a patch for this
to Mark.
> I have used the spi tree from next-20130822 for today.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/