linux-kernel - Re: [BUILD-FAILURE] 2.6.24-rc1-git8 build fails drivers/pci/probe.c

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: <20071101154044.GA12833@suse.de>
Date:	Thu, 1 Nov 2007 08:40:44 -0700
From:	Greg KH <gregkh@...e.de>
To:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andy Whitcroft <apw@...dowen.org>
Subject: Re: [BUILD-FAILURE] 2.6.24-rc1-git8 build fails drivers/pci/probe.c

On Wed, Oct 31, 2007 at 01:48:27PM +0530, Kamalesh Babulal wrote:
> Hi,
> 
> The 2.6.24-rc-git8 build fails with build error
> 
>   CC      drivers/pci/probe.o
> drivers/pci/probe.c: In function 'pci_create_legacy_files':
> drivers/pci/probe.c:56: error: implicit declaration of function 'class_device_create_bin_file'
> drivers/pci/probe.c: In function 'pci_remove_legacy_files':
> drivers/pci/probe.c:71: error: implicit declaration of function 'class_device_remove_bin_file'
> make[2]: *** [drivers/pci/probe.o] Error 1
> make[1]: *** [drivers/pci] Error 2
> make: *** [drivers] Error 2
> 
> This is caused by the commit fcd239d3d5575e5cc63aab5c33cf6dc66904f6d6 (Driver core: remove class_device_*_bin_file).
> These functions are still being used by drivers/pci/probe.c.

Thanks for the report, Linus's tree now has a fix for this oversight on
my behalf.

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/