From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: olof@lixom.net, linuxppc-dev@ozlabs.org
Subject: Re: [RFC/PATCH] Add a device_initcall to machdep_calls
Date: Sat, 01 Dec 2007 10:32:35 +1100 [thread overview]
Message-ID: <1196465556.13230.120.camel@pasglop> (raw)
In-Reply-To: <fa686aa40711301530k6001d563mb910f10b0d95503c@mail.gmail.com>
> Is that level of sophistication really warranted for this scenario?
It's not -that- sophisticated and I want to have access to all
init levels, not just device and I don't like adding ad-hoc ppc_md.
calls that much.
Ben.
prev parent reply other threads:[~2007-11-30 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 22:51 [RFC/PATCH] Add a device_initcall to machdep_calls Grant Likely
2007-11-30 22:58 ` Benjamin Herrenschmidt
2007-11-30 23:30 ` Grant Likely
2007-11-30 23:32 ` 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=1196465556.13230.120.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--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).