public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "René Bolldorf" <xsecute@googlemail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] drivers/pci/pci.c Section mismatch
Date: Fri, 19 Mar 2010 00:34:22 +0100	[thread overview]
Message-ID: <4BA2B87E.8050404@googlemail.com> (raw)
In-Reply-To: <4BA2B028.8060705@oracle.com>

On 03/18/10 23:58, Randy Dunlap wrote:
> On 03/18/10 15:08, Ren� Bolldorf wrote:
>> Signed-off-by: Rene Bolldorf<xsecute@googlemail.com>
>>
>> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
>> index ddd55dc..a1f7d93 100644
>> --- a/drivers/pci/pci.c
>> +++ b/drivers/pci/pci.c
>> @@ -2773,7 +2773,7 @@ int pci_resource_bar(struct pci_dev *dev, int
>> resno, enum pci_bar_type *type)
>>   /* Some architectures require additional programming to enable VGA */
>>   static arch_set_vga_state_t arch_set_vga_state;
>>
>> -void __init pci_register_set_vga_state(arch_set_vga_state_t func)
>> +void pci_register_set_vga_state(arch_set_vga_state_t func)
>>   {
>>       arch_set_vga_state = func;    /* NULL disables */
>>   }
>> --
>
> Hi,
>
> Please put the offending/warning messages in the patch description.
> Include your analysis if it isn't obvious.
>
> thanks,

Hi,

the warning message was:
WARNING: drivers/pci/built-in.o(__ksymtab+0x190): Section mismatch in 
reference from the variable __ksymtab_pci_register_set_vga_state to the 
function .init.text:pci_register_set_vga_state()
The symbol pci_register_set_vga_state is exported and annotated __init
Fix this by removing the __init annotation of pci_register_set_vga_state 
or drop the export.

$fgrep "pci_register_set_vga_state" `find .`

$./arch/x86/kernel/apic/x2apic_uv_x.c: 
pci_register_set_vga_state(uv_set_vga_state);
$./include/linux/pci.h:extern void 
pci_register_set_vga_state(arch_set_vga_state_t func);
$./drivers/pci/pci.c:void 
pci_register_set_vga_state(arch_set_vga_state_t func)
$./drivers/pci/pci.c:EXPORT_SYMBOL(pci_register_set_vga_state);

this is a volatile function that set's a spec. state and is only used 
from uv_system_init(arch/x86/kernel/apic/x2apic_uv_x.c), the macro can 
also be removed.

  reply	other threads:[~2010-03-18 23:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 22:08 [PATCH 4/5] drivers/pci/pci.c Section mismatch René Bolldorf
2010-03-18 22:58 ` Randy Dunlap
2010-03-18 23:34   ` René Bolldorf [this message]
2010-03-18 23:37     ` Randy Dunlap
2010-03-19  0:19       ` René Bolldorf

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=4BA2B87E.8050404@googlemail.com \
    --to=xsecute@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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