public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [patch 1/1] bk-acpi-acpi_pci_irq_disable build fix
Date: 17 Mar 2005 23:30:20 -0500	[thread overview]
Message-ID: <1111120217.9335.143.camel@d845pe> (raw)
In-Reply-To: <200503120957.j2C9vs7u000794-bipKiLWnuIsyyg0EjBt7GtHuzzzSOjJt@public.gmane.org>

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

      parent reply	other threads:[~2005-03-18  4:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-12  9:57 [patch 1/1] bk-acpi-acpi_pci_irq_disable build fix akpm-3NddpPZAyC0
     [not found] ` <200503120957.j2C9vs7u000794-bipKiLWnuIsyyg0EjBt7GtHuzzzSOjJt@public.gmane.org>
2005-03-18  4:30   ` Len Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1111120217.9335.143.camel@d845pe \
    --to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=akpm-3NddpPZAyC0@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox