From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Satyam Sharma" <satyam.sharma@gmail.com>
Cc: "Li Yang-r58472" <LeoLi@freescale.com>,
Andrew Morton <akpm@osdl.org>, Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, Linus <torvalds@linux-foundation.org>
Subject: Re: [PATCH 1/2] kbuild: Add "Section mismatch" warning whitelist for powerpc
Date: Tue, 15 May 2007 20:56:41 +1000 [thread overview]
Message-ID: <20070515205641.babf2ce9.sfr@canb.auug.org.au> (raw)
In-Reply-To: <a781481a0705150303y587ea18dt435f2fc45a671226@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Tue, 15 May 2007 15:33:50 +0530 "Satyam Sharma" <satyam.sharma@gmail.com> wrote:
>
> But I have slightly different (reversed) semantics for __init_refok
> in mind. Basically, we use __init_refok to annotate _callees_
> and not _callers_. In short, __init_refok is a _type_ of __init
> section that other sections can freely reference to, without
> modpost complaining about this. [ had suggested this in some
> previous thread earlier ]
But lots of __init routines cannot be called from just anywhere, it is
the special circumstances of some of the callers that makes the call from
non-init to init ok. So you need to mark the callers specially.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-15 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 10:53 Li Yang
2007-05-14 11:06 ` Sam Ravnborg
2007-05-14 13:56 ` Kumar Gala
2007-05-14 19:30 ` Andrew Morton
2007-05-14 20:10 ` Kumar Gala
2007-05-14 21:13 ` Sam Ravnborg
2007-05-15 0:17 ` Satyam Sharma
2007-05-15 9:22 ` Li Yang-r58472
2007-05-15 10:03 ` Satyam Sharma
2007-05-15 10:56 ` Stephen Rothwell [this message]
2007-05-15 9:36 ` Li Yang-r58472
2007-05-15 19:29 ` Sam Ravnborg
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=20070515205641.babf2ce9.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=LeoLi@freescale.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sam@ravnborg.org \
--cc=satyam.sharma@gmail.com \
--cc=torvalds@linux-foundation.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®