From: Arjan van de Ven <arjan@infradead.org>
To: "Tony Luck" <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] get rid if __cpuinit and __cpuexit
Date: Wed, 22 Oct 2008 18:07:37 -0700 [thread overview]
Message-ID: <20081022180737.289ab7ee@infradead.org> (raw)
In-Reply-To: <12c511ca0810221712n665b4c75t5d07c7f4d5e006b2@mail.gmail.com>
On Wed, 22 Oct 2008 17:12:14 -0700
"Tony Luck" <tony.luck@intel.com> wrote:
> On Wed, Oct 22, 2008 at 3:30 PM, Arjan van de Ven
> <arjan@infradead.org> wrote:
> > as discussed briefly at the kernel summit; __cpuinit and __cpuexit
> > are causing a ton more complexity than they're worth (just see how
> > many section warnings an average build has);
>
> Nice idea ... but on ia64 I actually see *more* section mismatch
> warnings with this patch applied :-(
>
> generic_defconfig goes up from 6 to 7
> tiger_defconfig rises from 3 to 6
interesting... I don't see how that can be unless the checks originally
had a bug and did not complain about a reference to __init(data) memory
from inside __cpuinit memory...
(in which case my point of this being too complex and fragile is
proven ;-)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-10-23 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 22:30 Arjan van de Ven
2008-10-23 0:12 ` Tony Luck
2008-10-23 1:07 ` Arjan van de Ven [this message]
2008-10-24 18:01 ` Tony Luck
2008-10-23 6:21 ` Alexey Dobriyan
2008-10-23 13:17 ` Arjan van de Ven
2008-10-23 13:43 ` Alexey Dobriyan
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=20081022180737.289ab7ee@infradead.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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®