All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: David Lebrun <david.lebrun@uclouvain.be>,
	"David S. Miller" <davem@davemloft.net>,
	David Vrabel <david.vrabel@citrix.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Michael Kelley <mikelley@microsoft.com>,
	Shannon Zhao <shannon.zhao@linaro.org>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the kbuild tree
Date: Thu, 2 Jun 2022 09:28:09 +1000	[thread overview]
Message-ID: <20220602092809.04008a86@canb.auug.org.au> (raw)

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

Hi all,

After merging the kbuild tree, today's linux-next build (arm
multi_v7_defconfig) produced these warnings:

WARNING: modpost: vmlinux.o(___ksymtab_gpl+mdio_bus_init+0x0): Section mismatch in reference from the variable __ksymtab_mdio_bus_init to the function .init.text:mdio_bus_init()
The symbol mdio_bus_init is exported and annotated __init 
Fix this by removing the __init annotation of mdio_bus_init or drop the export.

WARNING: modpost: vmlinux.o(___ksymtab+xfrm4_protocol_init+0x0): Section mismatch in reference from the variable __ksymtab_xfrm4_protocol_init to the function .init.text:xfrm4_protocol_init()
The symbol xfrm4_protocol_init is exported and annotated __init 
Fix this by removing the __init annotation of xfrm4_protocol_init or drop the export.

The x86_64 allmodconfig build added these:

WARNING: modpost: vmlinux.o(___ksymtab_gpl+xen_xlate_map_ballooned_pages+0x0): Section mismatch in reference from the variable __ksymtab_xen_xlate_map_ballooned_pages to the function .init.text:xen_xlate_map_ballooned_pages()
The symbol xen_xlate_map_ballooned_pages is exported and annotated __init 
Fix this by removing the __init annotation of xen_xlate_map_ballooned_pages or drop the export.

WARNING: modpost: vmlinux.o(___ksymtab_gpl+ixp4xx_timer_setup+0x0): Section mismatch in reference from the variable __ksymtab_ixp4xx_timer_setup to the function .init.text:ixp4xx_timer_setup()
The symbol ixp4xx_timer_setup is exported and annotated __init 
Fix this by removing the __init annotation of ixp4xx_timer_setup or drop the export.

WARNING: modpost: vmlinux.o(___ksymtab_gpl+hv_init_clocksource+0x0): Section mismatch in reference from the variable __ksymtab_hv_init_clocksource to the function .init.text:hv_init_clocksource()
The symbol hv_init_clocksource is exported and annotated __init 
Fix this by removing the __init annotation of hv_init_clocksource or drop the export.

WARNING: modpost: net/ipv6/ipv6.o(___ksymtab+seg6_hmac_init+0x0): Section mismatch in reference from the variable __ksymtab_seg6_hmac_init to the function .init.text:seg6_hmac_init()
The symbol seg6_hmac_init is exported and annotated __init 
Fix this by removing the __init annotation of seg6_hmac_init or drop the export.
Exposed by commit

  cf2cbe28c6a2 ("modpost: fix section mismatch check for exported init/exit sections")

Introduced by commits

  90eff9096c01 ("net: phy: Allow splitting MDIO bus/device support from PHYs")
  2f32b51b609f ("xfrm: Introduce xfrm_input_afinfo to access the the callbacks properly")
  243848fc018c ("xen/grant-table: Move xlated_setup_gnttab_pages to common place")
  13e0b4059b98 ("clocksource/drivers/ixp4xx: Add driver")
  dd2cb348613b ("clocksource/drivers: Continue making Hyper-V clocksource ISA agnostic")
  bf355b8d2c30 ("ipv6: sr: add core files for SR HMAC support")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2022-06-01 23:28 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01 23:28 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-04  0:13 linux-next: build warnings after merge of the kbuild tree Stephen Rothwell
2019-09-04  0:13 ` Stephen Rothwell
2019-09-04  1:00 ` Masahiro Yamada
2019-09-04  1:00   ` Masahiro Yamada
2019-09-04  6:22   ` Masahiro Yamada
2019-09-04  6:22     ` Masahiro Yamada
2019-09-04 12:33     ` Stephen Rothwell
2019-09-04 12:33       ` Stephen Rothwell
2019-09-04 12:32   ` Stephen Rothwell
2019-09-04 12:32     ` Stephen Rothwell
2018-05-30 22:40 Stephen Rothwell
2018-05-31  1:12 ` Masahiro Yamada
2018-05-31  1:26   ` Kees Cook
2018-05-31  3:53     ` Kees Cook
2018-06-01  1:56       ` Masahiro Yamada
2018-06-01  4:01         ` Kees Cook
2018-06-02 20:39           ` Arnd Bergmann
2018-06-04  8:39             ` Arnd Bergmann
2017-07-19  0:05 Stephen Rothwell
2016-08-17  1:44 Stephen Rothwell
2016-08-17 12:59 ` Michal Marek
2016-08-18  1:09   ` Nicholas Piggin
2016-08-19  3:38     ` Stephen Rothwell
2016-08-19  3:38       ` Stephen Rothwell
2016-08-19  5:09       ` Stephen Rothwell
2016-08-19  5:09         ` Stephen Rothwell
2016-08-19  5:32         ` Nicholas Piggin
2016-08-19  8:37         ` Michal Marek
2016-08-19 10:44           ` Nicholas Piggin
2016-08-19 10:44             ` Nicholas Piggin
2016-08-22 10:47             ` Nicholas Piggin
2016-08-26  3:58               ` Nicholas Piggin
2016-08-26  3:58                 ` Nicholas Piggin
2016-08-26  6:21                 ` Nicholas Mc Guire
2016-06-09  2:22 Stephen Rothwell
2016-06-09  2:56 ` Kees Cook
2016-06-09  4:05   ` Stephen Rothwell
2016-06-09 10:57     ` Michal Marek
2016-06-09 17:37       ` Emese Revfy
2016-06-09 17:58         ` Kees Cook
2016-06-09 11:10     ` Michael Ellerman
2016-06-09 17:42 ` Emese Revfy

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=20220602092809.04008a86@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=davem@davemloft.net \
    --cc=david.lebrun@uclouvain.be \
    --cc=david.vrabel@citrix.com \
    --cc=f.fainelli@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mikelley@microsoft.com \
    --cc=shannon.zhao@linaro.org \
    --cc=steffen.klassert@secunet.com \
    --cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.