mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	<linuxppc-dev@lists.ozlabs.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build warning after merge of the powerpc tree
Date: Thu, 19 May 2011 13:19:13 +1000	[thread overview]
Message-ID: <20110519131913.79c14fe7.sfr@canb.auug.org.au> (raw)

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

Hi all,

After merging the powerpc tree, today's linux-next build (powerpc
allyesconfig) produced this warning:

WARNING: arch/powerpc/sysdev/built-in.o(.text+0x10eb8): Section mismatch in reference from the function .ics_rtas_init() to the function .init.text:.xics_register_ics()
The function .ics_rtas_init() references
the function __init .xics_register_ics().
This is often because .ics_rtas_init lacks a __init 
annotation or the annotation of .xics_register_ics is wrong.

Introduced by commit 0b05ac6e2480 ("powerpc/xics: Rewrite XICS driver").

ics_rtas_init() is only called from xics_init() which is marked __init,
so ics_rtas_init() should be as well.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2011-05-19  3:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19  3:19 Stephen Rothwell [this message]
2015-10-20  5:21 Stephen Rothwell
2015-10-20 10:06 ` Michael Ellerman
2015-10-20 20:45   ` Stephen Rothwell
2017-09-04  8:53 Stephen Rothwell
2017-09-04  8:59 ` Cédric Le Goater
2019-11-13 22:34 Stephen Rothwell
2021-04-14 23:36 Stephen Rothwell
2021-04-15  8:52 Stephen Rothwell
2021-04-16 10:54 ` Michael Ellerman
2021-08-23  9:55 Stephen Rothwell
2021-08-23 10:48 ` Stephen Rothwell
2021-08-23 14:19   ` Jonathan Corbet
2021-08-23 23:21     ` Stephen Rothwell
2021-08-24  5:18   ` Aneesh Kumar K.V
2021-08-24 13:46     ` Jonathan Corbet
2023-02-16  3:40 Stephen Rothwell
2023-02-16 18:06 ` Josh Poimboeuf
2023-02-17  1:35   ` Michael Ellerman
2023-02-17  7:05     ` Josh Poimboeuf
2024-05-15  6:37 Stephen Rothwell
2024-05-16  2:42 ` Michael Ellerman
2024-05-16  4:36   ` Stephen Rothwell
2024-11-20  6:13 Stephen Rothwell
2025-02-19  4:46 Stephen Rothwell
2025-02-19  5:23 ` Madhavan Srinivasan
2025-02-19  5:49 ` Andrew Donnellan
2025-04-29  8:17 Stephen Rothwell
2025-04-29  8:57 Stephen Rothwell
2025-05-13 10:28 Stephen Rothwell
2025-05-29 23:44 ` Stephen Rothwell
2025-05-30 13:10   ` Athira Rajeev

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=20110519131913.79c14fe7.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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

all inboxes | Powered by JetHome®