From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: linux-next: build warning after merge of the gpio tree
Date: Tue, 5 Nov 2019 17:43:59 +1100 [thread overview]
Message-ID: <20191105174359.01cb034f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
Hi all,
After merging the gpio tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
WARNING: vmlinux.o(.data+0xbd3f4): Section mismatch in reference from the variable bcm_iproc_gpio_driver to the (unknown reference) .init.rodata:(unknown)
The variable bcm_iproc_gpio_driver references
the (unknown reference) __initconst (unknown)
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 similar for x86_64 allmodconfig)
Introduced by commit
6a41b6c5fc20 ("gpio: Add xgs-iproc driver")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-11-05 6:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 6:43 Stephen Rothwell [this message]
2019-11-07 8:35 ` linux-next: build warning after merge of the gpio tree Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2020-10-02 8:36 Stephen Rothwell
2020-01-09 4:16 Stephen Rothwell
2019-06-27 8:19 Stephen Rothwell
2019-06-27 14:57 ` Linus Walleij
2019-02-25 4:52 Stephen Rothwell
2018-12-18 5:41 Stephen Rothwell
2018-11-06 1:15 Stephen Rothwell
2018-11-06 7:24 ` Uwe Kleine-König
2018-01-11 4:06 Stephen Rothwell
2018-01-11 9:19 ` Linus Walleij
2017-05-30 3:52 Stephen Rothwell
2016-11-14 5:31 Stephen Rothwell
2016-09-13 3:18 Stephen Rothwell
2016-06-16 4:32 Stephen Rothwell
2016-06-16 10:02 ` Linus Walleij
2014-03-07 3:59 Stephen Rothwell
2014-03-07 6:16 ` Linus Walleij
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=20191105174359.01cb034f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).