All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney.cavm@gmail.com>
To: Thierry Reding <thierry.reding@avionic-design.de>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	linux-pci@vger.kernel.org
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: PCI Section mismatch error in linux-next.
Date: Fri, 17 Aug 2012 10:36:21 -0700	[thread overview]
Message-ID: <502E8115.90507@gmail.com> (raw)

For MIPS, Thierry Reding's patch in linux-next (PCI: Keep 
pci_fixup_irqs() around after init) causes:

WARNING: vmlinux.o(.text+0x22c784): Section mismatch in reference from 
the function pci_fixup_irqs() to the function 
.init.text:pcibios_update_irq()

The MIPS implementation of pcibios_update_irq() is __init, so there is 
conflict with the removal of __init from pci_fixup_irqs() and 
pdev_fixup_irq().

Can you guys either remove the patch from linux-next, or improve it to 
also fix up any architecture implementations of pdev_update_irq()?


Thanks,
David Daney

             reply	other threads:[~2012-08-17 17:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 17:36 David Daney [this message]
2012-08-17 17:44 ` PCI Section mismatch error in linux-next Bjorn Helgaas
2012-08-17 18:29   ` Thierry Reding
2012-08-17 19:32     ` Bjorn Helgaas
2012-08-17 20:07       ` Thierry Reding
2012-08-17 20:39         ` Bjorn Helgaas
2012-08-17 20:48           ` Thierry Reding
2012-08-17 21:06             ` Bjorn Helgaas
2012-08-17 21:22               ` Thierry Reding
2012-08-17 21:07             ` Thierry Reding
2012-08-17 21:25               ` Bjorn Helgaas
2012-08-17 21:32                 ` Thierry Reding
2012-08-17 21:46                   ` Bjorn Helgaas
2012-08-17 21:46                     ` Bjorn Helgaas
2012-08-20  5:30                   ` Greg KH
2012-08-20  7:16                     ` Thierry Reding
2012-08-21 14:32                     ` Geert Uytterhoeven
2012-08-21 17:04                       ` Ralf Baechle
2012-08-21 18:15                         ` Geert Uytterhoeven

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=502E8115.90507@gmail.com \
    --to=ddaney.cavm@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=thierry.reding@avionic-design.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.