linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Borislav Petkov <bp@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings in Linus' tree
Date: Tue, 23 Nov 2021 09:44:19 +1100	[thread overview]
Message-ID: <20211123094419.08000327@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 6363 bytes --]

Hi all,

Building Linus' tree, today's linux-next build (x86_64 allmodconfig)
produced these warnings:

WARNING: modpost: vmlinux.o(.text.unlikely+0x63df): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:builtin_cmdline
The function prepare_command_line() references
the variable __initdata builtin_cmdline.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of builtin_cmdline is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x63fa): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:builtin_cmdline
The function prepare_command_line() references
the variable __initdata builtin_cmdline.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of builtin_cmdline is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x640b): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:boot_command_line
The function prepare_command_line() references
the variable __initdata boot_command_line.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of boot_command_line is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x6412): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:builtin_cmdline
The function prepare_command_line() references
the variable __initdata builtin_cmdline.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of builtin_cmdline is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x6423): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:builtin_cmdline
The function prepare_command_line() references
the variable __initdata builtin_cmdline.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of builtin_cmdline is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x6461): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:builtin_cmdline
The function prepare_command_line() references
the variable __initdata builtin_cmdline.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of builtin_cmdline is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x6468): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:boot_command_line
The function prepare_command_line() references
the variable __initdata boot_command_line.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of boot_command_line is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x6474): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:boot_command_line
The function prepare_command_line() references
the variable __initdata boot_command_line.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of boot_command_line is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x647f): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:boot_command_line
The function prepare_command_line() references
the variable __initdata boot_command_line.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of boot_command_line is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x6487): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:boot_command_line
The function prepare_command_line() references
the variable __initdata boot_command_line.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of boot_command_line is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x6498): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:boot_command_line
The function prepare_command_line() references
the variable __initdata boot_command_line.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of boot_command_line is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x649f): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:command_line
The function prepare_command_line() references
the variable __initdata command_line.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of command_line is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x64b8): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:command_line
The function prepare_command_line() references
the variable __initdata command_line.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of command_line is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x64c3): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:command_line
The function prepare_command_line() references
the variable __initdata command_line.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of command_line is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x64c9): Section mismatch in reference from the function prepare_command_line() to the function .init.text:parse_early_param()
The function prepare_command_line() references
the function __init parse_early_param().
This is often because prepare_command_line lacks a __init 
annotation or the annotation of parse_early_param is wrong.

WARNING: modpost: vmlinux.o(.text.unlikely+0x64d0): Section mismatch in reference from the function prepare_command_line() to the variable .init.data:command_line
The function prepare_command_line() references
the variable __initdata command_line.
This is often because prepare_command_line lacks a __initdata 
annotation or the annotation of command_line is wrong.

Introduced by commit

  8d48bf8206f7 ("x86/boot: Pull up cmdline preparation and early param parsing")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-11-22 22:44 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 22:44 Stephen Rothwell [this message]
2021-11-23  7:04 ` linux-next: build warnings in Linus' tree Borislav Petkov
2021-11-24 12:30   ` [tip: x86/urgent] x86/boot: Mark prepare_command_line() __init tip-bot2 for Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2022-06-14  6:57 linux-next: build warnings in Linus' tree Stephen Rothwell
2022-05-26  7:21 Stephen Rothwell
2022-01-27  4:30 Stephen Rothwell
2022-01-27  6:01 ` Christoph Hellwig
2022-01-27 16:44   ` Stephen Rothwell
2022-01-27  4:24 Stephen Rothwell
2021-11-05  5:03 Stephen Rothwell
2021-10-12 10:56 Stephen Rothwell
2021-10-12 20:13 ` Randy Dunlap
2021-10-08  5:47 Stephen Rothwell
2021-10-10 21:27 ` Stephen Rothwell
2021-10-11 20:42   ` Rob Herring
2021-10-12 14:39     ` Arnd Bergmann
2021-10-13 22:12       ` Anatolij Gustschin
2021-10-13 22:17         ` Rob Herring
2021-10-13 22:28           ` Anatolij Gustschin
2021-10-13 23:22             ` Rob Herring
2021-10-14  8:44         ` Arnd Bergmann
2021-10-14 12:24           ` Anatolij Gustschin
2020-09-07 23:11 Stephen Rothwell
2020-09-08 13:14 ` Josh Poimboeuf
2020-09-09  0:15   ` Stephen Rothwell
2020-04-03 22:19 Stephen Rothwell
2020-04-03 23:16 ` Rob Herring
2020-04-03 23:31   ` Nicolas Saenz Julienne
2017-11-13 21:52 Stephen Rothwell
2017-11-13 22:03 ` Linus Torvalds
2013-07-04  4:58 Stephen Rothwell
2013-07-09 21:48 ` Nikolova, Tatyana E
2011-08-15  1:57 Stephen Rothwell
2011-05-23  1:25 Stephen Rothwell
2011-05-23  2:31 ` Eduardo Silva
2011-01-14  0:17 Stephen Rothwell
2011-01-14  0:09 Stephen Rothwell
2011-01-14  0:17 ` Andrew Morton
2011-01-14  1:06   ` Greg KH
2010-08-17  1:24 Stephen Rothwell
2010-08-30  1:42 ` Stephen Rothwell
2010-08-30  6:08   ` Zhang Rui
2010-09-03  2:01     ` Stephen Rothwell
2010-09-03  2:36     ` Len Brown
2010-09-17  4:26     ` Stephen Rothwell
2010-09-27 13:31       ` Stephen Rothwell
2010-08-07  2:21 Stephen Rothwell
2010-08-07  8:13 ` Vikas Chaudhary

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=20211123094419.08000327@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).