Re: 2.6.23-rc3-git3 make warnings

[Greg KH <greg@kroah.com>]

On Wed, Aug 22, 2007 at 12:17:23AM +0800, WANG Cong wrote:
> On Tue, Aug 21, 2007 at 03:20:38PM +0200, Jarek Poplawski wrote:
> >Here are some more of, probably well-known, warnings with attached
> >testing-only .config.
> >
> >Regards,
> >Jarek P.
> >
> >
> >sed: -e expression #1, char 154: Unknown option to 's'
> >drivers/acpi/ec.c: In function `acpi_ec_ecdt_probe':
> >drivers/acpi/ec.c:873: warning: passing arg 1 of `acpi_get_devices' discards qualifiers from pointer target type
> >drivers/pci/search.c: In function `pci_find_slot':
> >drivers/pci/search.c:99: warning: `pci_find_device' is deprecated (declared at include/linux/pci.h:480)
> >drivers/pci/search.c: At top level:
> >drivers/pci/search.c:437: warning: `pci_find_device' is deprecated (declared at drivers/pci/search.c:244)
> >drivers/pci/search.c:437: warning: `pci_find_device' is deprecated (declared at drivers/pci/search.c:244)
> >drivers/pci/search.c:438: warning: `pci_find_slot' is deprecated (declared at drivers/pci/search.c:96)
> >drivers/pci/search.c:438: warning: `pci_find_slot' is deprecated (declared at drivers/pci/search.c:96)
> >drivers/pci/msi.c:686: warning: weak declaration of `arch_msi_check_device' after first use results in unspecified behavior
> >drivers/pci/msi.c:698: warning: weak declaration of `arch_setup_msi_irqs' after first use results in unspecified behavior
> >drivers/pci/msi.c:718: warning: weak declaration of `arch_teardown_msi_irqs' after first use results in unspecified behavior
> >In file included from drivers/usb/host/ohci-hcd.c:859:
> >drivers/usb/host/ohci-pci.c: In function `ohci_pci_start':
> >drivers/usb/host/ohci-pci.c:202: warning: unused variable `pdev'
> 				^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> This warning is suspicious. In fact, 'pdev' is used when CONFIG_PM is defined.
> See the following:
> 
> <snip>
>                 if (device_may_wakeup(&pdev->dev))
>                         ohci->hc_control |= OHCI_CTRL_RWC;
> <snip>
> 
> Or a bug of gcc?

gcc bug, I have a patch for this queued up.

thanks,

greg k-h