public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Helge Deller <deller@gmx.de>
Cc: Shang XiaoJing <shangxiaojing@huawei.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the fbdev tree
Date: Tue, 15 Nov 2022 11:20:21 +1100	[thread overview]
Message-ID: <20221115112021.1c8aa004@canb.auug.org.au> (raw)

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

Hi all,

After merging the fbdev tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

WARNING: modpost: drivers/video/fbdev/via/viafb.o: section mismatch in reference: init_module (section: .init.text) -> viafb_exit (section: .exit.text)

Introduced by commit

  ab885d8c7e15 ("fbdev: via: Fix error in via_core_init()")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2022-11-15  0:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15  0:20 Stephen Rothwell [this message]
2022-11-15  5:20 ` linux-next: build warning after merge of the fbdev tree Helge Deller
  -- strict thread matches above, loose matches on Subject: below --
2019-06-11  0:42 Stephen Rothwell
2019-04-01 22:30 Stephen Rothwell
2019-04-02 12:38 ` Tom Li
2019-04-02 15:16   ` Bartlomiej Zolnierkiewicz
2017-08-02  1:32 Stephen Rothwell
2011-12-20  5:32 Stephen Rothwell
2011-12-20 10:37 ` Laurent Pinchart
2011-12-20 13:48   ` Geert Uytterhoeven
2011-12-20 15:19     ` Laurent Pinchart
2011-12-20 15:24       ` Geert Uytterhoeven
2011-12-20 15:42         ` Laurent Pinchart
2011-12-20 15:48           ` Geert Uytterhoeven

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=20221115112021.1c8aa004@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=shangxiaojing@huawei.com \
    /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