public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: powernow-k8: section mismatch
Date: Wed, 26 May 2010 00:04:33 +0200	[thread overview]
Message-ID: <20100525220433.GB28552@aftab> (raw)
In-Reply-To: <tkrat.97946ecfb316e3af@s5r6.in-berlin.de>

From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Date: Tue, May 25, 2010 at 04:10:03PM -0400

> Hi,
> 
> I got the following with current git:
> 
>     WARNING: arch/x86/kernel/cpu/cpufreq/powernow-k8.o(.exit.text+0x1c): Section mismatch in reference from the function cleanup_module() to the variable .cpuinit.data:cpb_nb                      
>     The function __exit cleanup_module() references                                                 
>     a variable __cpuinitdata cpb_nb.                                                                
>     This is often seen when error handling in the exit function                                     
>     uses functionality in the init path.                                                            
>     The fix is often to remove the __cpuinitdata annotation of                                      
>     cpb_nb so it may be used outside an init section.                                               
> 
> Looks like it was introduced by
> "powernow-k8: Add core performance boost support".

Oh yeah, Peter pointed it out to me earlier, we have a fix already:
https://patchwork.kernel.org/patch/102225/

Thanks.

-- 
Regards/Gruss,
Boris.

Operating Systems Research Center
Advanced Micro Devices, Inc.

      reply	other threads:[~2010-05-25 22:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25 20:10 powernow-k8: section mismatch Stefan Richter
2010-05-25 22:04 ` Borislav Petkov [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=20100525220433.GB28552@aftab \
    --to=bp@amd64.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox