From: Stephen Rothwell <sfr@canb.auug.org.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] PCI: Provide a default pcibios_update_irq()
Date: Wed, 19 Sep 2012 22:37:31 +0000 [thread overview]
Message-ID: <20120920083731.b99255eb8fdeea908d34ed2f@canb.auug.org.au> (raw)
In-Reply-To: <1347880974-13615-2-git-send-email-thierry.reding@avionic-design.de>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
Hi,
On Mon, 17 Sep 2012 13:22:54 +0200 Thierry Reding <thierry.reding@avionic-design.de> wrote:
>
> diff --git a/drivers/pci/setup-irq.c b/drivers/pci/setup-irq.c
> index 270ae7b..3d61ce3 100644
> --- a/drivers/pci/setup-irq.c
> +++ b/drivers/pci/setup-irq.c
> @@ -17,6 +17,11 @@
> #include <linux/ioport.h>
> #include <linux/cache.h>
>
> +void __weak pcibios_update_irq(struct pci_dev *dev, int irq)
> +{
> + dev_dbg(&dev->dev, "Assigning IRQ %02d\n", irq);
> + pci_write_config_byte(dev, PCI_INTERRUPT_LINE, irq);
> +}
>
> static void
> pdev_fixup_irq(struct pci_dev *dev,
Didn't we have a problem with some compiler versions when the weak
definition was in the same file as the call (there is a call to this
function in drivers/pci/setup-irq.c)?
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-09-19 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 11:22 [PATCH v2 1/2] PCI: Keep pci_fixup_irqs() around after init Thierry Reding
2012-09-17 11:22 ` [PATCH v2 2/2] PCI: Provide a default pcibios_update_irq() Thierry Reding
2012-09-19 22:37 ` Stephen Rothwell [this message]
2012-09-17 11:34 ` [PATCH v2 1/2] PCI: Keep pci_fixup_irqs() around after init Greg Kroah-Hartman
2012-09-19 16:57 ` Bjorn Helgaas
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=20120920083731.b99255eb8fdeea908d34ed2f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).