From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org, olof@lixom.net
Subject: Re: [PATCH] [POWERPC] Add machine initcall macros
Date: Sat, 01 Dec 2007 18:26:01 +1100 [thread overview]
Message-ID: <1196493961.13230.134.camel@pasglop> (raw)
In-Reply-To: <1196493067.17582.7.camel@concordia>
On Sat, 2007-12-01 at 18:11 +1100, Michael Ellerman wrote:
> I can't think at the moment, it's Saturday, but is there some way we
> could just make it a wrapper macro, so we don't need to redefine - and
> keep in sync - all the different init call types?
>
> So the usage would look something like:
>
> arch_initcall(machine_initcall(foo, bar));
>
> or
>
> machine_initcall(foo, arch_initcall(bar));
Not really. I'd like to turn that into magic ELF sections ultimately, in
which case your trick above wouldn't work... besides, it's clumsy :-)
Ben.
prev parent reply other threads:[~2007-12-01 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 0:24 [PATCH] [POWERPC] Add machine initcall macros Grant Likely
2007-12-01 5:10 ` Benjamin Herrenschmidt
2007-12-01 7:11 ` Michael Ellerman
2007-12-01 7:26 ` Benjamin Herrenschmidt [this message]
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=1196493961.13230.134.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=olof@lixom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).