From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: "Paweł Sikora" <pluto@agmk.net>,
"Linux Kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: smart gcc inliner...
Date: Tue, 27 Mar 2007 19:55:38 -0700 [thread overview]
Message-ID: <4609D92A.3050104@goop.org> (raw)
In-Reply-To: <p73ircm4odz.fsf@bingen.suse.de>
Andi Kleen wrote:
> init functions should only ever be called from other init functions.
>
> So this should not happen. If it happens the annotations need to be fixed.
>
I've seen some versions of gcc inline weak functions too.
J
next prev parent reply other threads:[~2007-03-28 2:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 15:07 smart gcc inliner Paweł Sikora
2007-03-27 16:55 ` Andi Kleen
2007-03-28 2:55 ` Jeremy Fitzhardinge [this message]
2007-03-30 19:32 ` Adrian Bunk
2007-03-30 19:39 ` Jeremy Fitzhardinge
2007-03-28 2:05 ` Jan Engelhardt
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=4609D92A.3050104@goop.org \
--to=jeremy@goop.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pluto@agmk.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.