public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mauro Carvalho Chehab <mchehab@redhat•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Aristeu Rozanski <aris@redhat•com>,
	Rusty Russell <rusty@rustcorp•com.au>
Subject: linux-next: i7core_edac tree build failure
Date: Thu, 12 Nov 2009 16:58:52 +1100	[thread overview]
Message-ID: <20091112165852.855d1e5d.sfr@canb.auug.org.au> (raw)

Hi Mauro,

Today's linux-next build (x86_64 allmodconfig) failed like this:

tmp_exports-asm.o: In function `__ksymtab_pci_legacy_init':
(__ksymtab_gpl_sorted+0x3120): undefined reference to `pci_legacy_init'

Caused by commit a120a84ebbc4cbc9c1addddd2b491e3683b842a6 ("pci: Add a
probing code that seeks for an specific bus") (which applies
EXPORT_SYMBOL_GPL() to a static function) interacting with the rr tree's
changes.

I have applied the following patch for today:

From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Thu, 12 Nov 2009 16:55:38 +1100
Subject: [PATCH] i7core_edac: do not export static functions

Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
 arch/x86/pci/legacy.c |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/arch/x86/pci/legacy.c b/arch/x86/pci/legacy.c
index 5e22d83..a8194c8 100644
--- a/arch/x86/pci/legacy.c
+++ b/arch/x86/pci/legacy.c
@@ -38,7 +38,6 @@ static int __init pci_legacy_init(void)
 
 	return 0;
 }
-EXPORT_SYMBOL_GPL(pci_legacy_init);
 
 void pcibios_scan_specific_bus(int busn)
 {
-- 
1.6.5.2

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

             reply	other threads:[~2009-11-12  5:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12  5:58 Stephen Rothwell [this message]
2009-11-12 13:10 ` linux-next: i7core_edac tree build failure Rusty Russell
2009-11-12 23:54   ` Stephen Rothwell
2009-11-15 23:30     ` Stephen Rothwell
2009-12-02  2:11       ` Stephen Rothwell

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=20091112165852.855d1e5d.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=aris@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mchehab@redhat$(echo .)com \
    --cc=rusty@rustcorp$(echo .)com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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