From: David Miller <davem@davemloft.net>
To: sam@ravnborg.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bogus section mismatch errors?
Date: Tue, 08 May 2007 13:41:01 -0700 (PDT) [thread overview]
Message-ID: <20070508.134101.122616112.davem@davemloft.net> (raw)
In-Reply-To: <20070508115220.GA29160@uranus.ravnborg.org>
From: Sam Ravnborg <sam@ravnborg.org>
Date: Tue, 8 May 2007 13:52:20 +0200
> There are in slab a function that is not marked __init that refer to a function marked
> __init. But the logic surrounding makes it OK.
>
> I have no fix/workaround for this.
> Andres has suggested that we should mark functions/data that may refer to __init{data}
> with something like: __nowarn and __nowarndata
>
> I am planning to implement something so we can mark functions/data with:
> __init_ref_ok and _init_data_ref_ok
> Which is indeed more ugly but expalins what is actually OK.
>
> I hope to take a look during the weekend.
Thanks for working on this, it's the only mismatch I still see
on sparc64 in current GIT :-)
next prev parent reply other threads:[~2007-05-08 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 11:17 Russell King
2007-05-08 11:52 ` Sam Ravnborg
2007-05-08 20:41 ` David Miller [this message]
2007-05-09 9:59 ` Paul Mundt
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=20070508.134101.122616112.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
Powered by JetHome