linux-kernel - Re: randconfig build error with next-20150113, in drivers/pcmcia/rsrc

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]

Date:	Tue, 13 Jan 2015 10:11:59 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Jim Davis <jim.epost@...il.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next <linux-next@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	alan@...ux.intel.com, linux-pcmcia@...ts.infradead.org
Subject: Re: randconfig build error with next-20150113, in
 drivers/pcmcia/rsrc_pci.c

On Tue, Jan 13, 2015 at 11:08:30AM -0700, Jim Davis wrote:
> Building with the attached random configuration file,
> 
> drivers/pcmcia/rsrc_pci.c: In function ‘find_io_region’:
> drivers/pcmcia/rsrc_pci.c:40:2: error: implicit declaration of
> function ‘pci_bus_alloc_resource’
> [-Werror=implicit-function-declaration]
>   ret = pci_bus_alloc_resource(s->cb_dev->bus, res, num, 1,
>   ^
> drivers/pcmcia/rsrc_pci.c:40:40: error: dereferencing pointer to incomplete type
>   ret = pci_bus_alloc_resource(s->cb_dev->bus, res, num, 1,
>                                         ^
> drivers/pcmcia/rsrc_pci.c: In function ‘res_pci_find_mem’:
> drivers/pcmcia/rsrc_pci.c:144:40: error: dereferencing pointer to
> incomplete type
>   ret = pci_bus_alloc_resource(s->cb_dev->bus,
>                                         ^
> cc1: some warnings being treated as errors
> make[2]: *** [drivers/pcmcia/rsrc_pci.o] Error 1

I have a patch from Arnd to fix this that I'll queue up soon, thanks.

greg k-h
--
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/