LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Christian Zigotzky <chzigotzky@xenosoft.de>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Christian Zigotzky <info@xenosoft.de>
Subject: Re: Latest Git kernel: Section mismatch in reference from the variable start_here_multiplatform to the function .init.text:.early_setup()
Date: Wed, 15 May 2019 12:15:49 +0200	[thread overview]
Message-ID: <dbfbd2e0-eca8-8ecc-793b-a6f1471ce2ee@c-s.fr> (raw)
In-Reply-To: <d8d0bf05-2c22-0ade-6361-4841e521597c@xenosoft.de>

Hi,

Le 15/05/2019 à 12:09, Christian Zigotzky a écrit :
> Hi All,
> 
> I got the following error messages with the latest Git kernel today:
> 
> GEN     .version
>    CHK     include/generated/compile.h
>    LD      vmlinux.o
>    MODPOST vmlinux.o
> WARNING: vmlinux.o(.text+0x302a): Section mismatch in reference from the 
> variable start_here_multiplatform to the function .init.text:.early_setup()
> The function start_here_multiplatform() references
> the function __init .early_setup().
> This is often because start_here_multiplatform lacks a __init
> annotation or the annotation of .early_setup is wrong.
> 
>    MODINFO modules.builtin.modinfo
>    KSYM    .tmp_kallsyms1.o
>    KSYM    .tmp_kallsyms2.o
>    LD      vmlinux
>    SORTEX  vmlinux
>    SYSMAP  System.map
>    CHKHEAD vmlinux
> 
> What does it mean?

I proposed a patch for it at https://patchwork.ozlabs.org/patch/1097845/

Christophe

> 
> Please find attached the kernel config.
> 
> Thanks,
> Christian
> 

  reply	other threads:[~2019-05-15 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15 10:09 Latest Git kernel: Section mismatch in reference from the variable start_here_multiplatform to the function .init.text:.early_setup() Christian Zigotzky
2019-05-15 10:15 ` Christophe Leroy [this message]
2019-05-16 11:06   ` Shawn Landden
2019-06-10  9:39   ` Christian Zigotzky
2019-06-10 20:09     ` Christophe Leroy

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=dbfbd2e0-eca8-8ecc-793b-a6f1471ce2ee@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=chzigotzky@xenosoft.de \
    --cc=info@xenosoft.de \
    --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