LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: linuxppc-dev@lists.ozlabs.org, geert@linux-m68k.org
Subject: Section mismatch in reference from the variable via_pmu_driver
Date: Sat, 24 May 2014 17:35:31 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.19.4.1405241720190.7552@trent.utfs.org> (raw)

Hi,

while compiling 3.15-rc6 for powerpc (gcc-4.8.1 crosscompiler on x86_64), 
a warning popped up:

   WARNING: modpost: Found 1 section mismatch(es).

Compiling with CONFIG_DEBUG_SECTION_MISMATCH=y gives:

-----------------------------------
  LD      drivers/macintosh/built-in.o
  CC [M]  fs/hfsplus/inode.o
WARNING: drivers/macintosh/built-in.o(.data+0x184): Section mismatch in 
reference from the variable via_pmu_driver to the function 
.init.text:pmu_init()
The variable via_pmu_driver references
the function __init pmu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the 
variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console
-----------------------------------

...and, later on:

-----------------------------------
  LD      drivers/built-in.o
WARNING: drivers/built-in.o(.data+0x488c): Section mismatch in reference 
from the variable via_pmu_driver to the function .init.text:pmu_init()
The variable via_pmu_driver references
the function __init pmu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the 
variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console

  LINK    vmlinux
  LD      vmlinux.o
  MODPOST vmlinux.o
WARNING: vmlinux.o(.data+0x1ff44): Section mismatch in reference from the 
variable via_pmu_driver to the function .init.text:pmu_init()
The variable via_pmu_driver references
the function __init pmu_init()
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the 
variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console
-----------------------------------

This had been reported [0] by Geert for v3.3-rc1 back in 2012, and maybe 
the warning was always there, but I didn't notice it until now.

Oh, and after everything has been built, this happens:

-----------------------------------
INFO: Uncompressed kernel (size 0x6714a0) overlaps the address of the wrapper(0x400000)
INFO: Fixing the link_address of wrapper to (0x700000)
-----------------------------------

...but I think this was always printed after compiling a kernel for 
PowerPC, I just just I should mention it (again [1]).

Thanks,
Christian.

[0] https://lkml.org/lkml/2012/1/22/17
[1] https://lkml.org/lkml/2012/4/4/140
-- 
BOFH excuse #30:

positron router malfunction

                 reply	other threads:[~2014-05-25  0:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.DEB.2.19.4.1405241720190.7552@trent.utfs.org \
    --to=lists@nerdbynature.de \
    --cc=geert@linux-m68k.org \
    --cc=linuxppc-dev@lists.ozlabs.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