[patch 1/1] bk-acpi-acpi_pci_irq_disable build fix

[patch 1/1] bk-acpi-acpi_pci_irq_disable build fix

[akpm-3NddpPZAyC0]

drivers/acpi/pci_irq.c: In function `acpi_pci_irq_disable':
drivers/acpi/pci_irq.c:495: error: too few arguments to function `acpi_pci_irq_lookup'
drivers/acpi/pci_irq.c:502: error: too few arguments to function `acpi_pci_irq_derive'

Wild-assed guess:

Signed-off-by: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>
---

 25-akpm/drivers/acpi/pci_irq.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff -puN drivers/acpi/pci_irq.c~bk-acpi-acpi_pci_irq_disable-build-fix drivers/acpi/pci_irq.c
--- 25/drivers/acpi/pci_irq.c~bk-acpi-acpi_pci_irq_disable-build-fix	2005-03-12 01:57:08.000000000 -0800
+++ 25-akpm/drivers/acpi/pci_irq.c	2005-03-12 01:57:08.000000000 -0800
@@ -482,14 +482,14 @@ acpi_pci_irq_disable (
 	 * First we check the PCI IRQ routing table (PRT) for an IRQ.
 	 */
  	gsi = acpi_pci_irq_lookup(dev->bus, PCI_SLOT(dev->devfn), pin,
-				  &edge_level, &active_high_low);
+				  &edge_level, &active_high_low, NULL);
 	/*
 	 * If no PRT entry was found, we'll try to derive an IRQ from the
 	 * device's parent bridge.
 	 */
 	if (gsi < 0)
  		gsi = acpi_pci_irq_derive(dev, pin,
-					  &edge_level, &active_high_low);
+					  &edge_level, &active_high_low, NULL);
 	if (gsi < 0)
 		return_VOID;
 
_


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: [patch 1/1] bk-acpi-acpi_pci_irq_disable build fix

[Len Brown]

Applied.

thanks,
-Len

On Sat, 2005-03-12 at 04:57, akpm-3NddpPZAyC0@public.gmane.org wrote:
> 
> drivers/acpi/pci_irq.c: In function `acpi_pci_irq_disable':
> drivers/acpi/pci_irq.c:495: error: too few arguments to function
> `acpi_pci_irq_lookup'
> drivers/acpi/pci_irq.c:502: error: too few arguments to function
> `acpi_pci_irq_derive'
> 
> Wild-assed guess:
> 
> Signed-off-by: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>
> ---
> 
>  25-akpm/drivers/acpi/pci_irq.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff -puN
> drivers/acpi/pci_irq.c~bk-acpi-acpi_pci_irq_disable-build-fix
> drivers/acpi/pci_irq.c
> ---
> 25/drivers/acpi/pci_irq.c~bk-acpi-acpi_pci_irq_disable-build-fix   
> 2005-03-12 01:57:08.000000000 -0800
> +++ 25-akpm/drivers/acpi/pci_irq.c      2005-03-12 01:57:08.000000000
> -0800
> @@ -482,14 +482,14 @@ acpi_pci_irq_disable (
>          * First we check the PCI IRQ routing table (PRT) for an IRQ.
>          */
>         gsi = acpi_pci_irq_lookup(dev->bus, PCI_SLOT(dev->devfn), pin,
> -                                 &edge_level, &active_high_low);
> +                                 &edge_level, &active_high_low,
> NULL);
>         /*
>          * If no PRT entry was found, we'll try to derive an IRQ from
> the
>          * device's parent bridge.
>          */
>         if (gsi < 0)
>                 gsi = acpi_pci_irq_derive(dev, pin,
> -                                         &edge_level,
> &active_high_low);
> +                                         &edge_level,
> &active_high_low, NULL);
>         if (gsi < 0)
>                 return_VOID;
> 
> _
> 
> 



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click