From: Frank Rowand <frowand.list@gmail.com>
To: "Bird, Tim" <Tim.Bird@sonymobile.com>
Cc: Nicolas Pitre <nico@fluxnic.net>,
Grant Likely <grant.likely@secretlab.ca>,
Borislav Petkov <bp@alien8.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>,
Dirk Behme <dirk.behme@gmail.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
"tim.bird@am.sony.com" <tim.bird@am.sony.com>
Subject: Re: Why is the deferred initcall patch not mainline?
Date: Wed, 22 Oct 2014 02:49:23 -0700 [thread overview]
Message-ID: <54477DA3.3040605@gmail.com> (raw)
In-Reply-To: <F5184659D418E34EA12B1903EE5EF5FD01BCD433E681@seldmbx02.corpusers.net>
On 10/21/2014 12:37 PM, Bird, Tim wrote:
< snip >
> With regards to doing it dynamically, I'd have to think about how
> to do that. Having text-based lists of things to do at runtime seems
> to fit with how we're using device tree these days, but I'm not sure
> how that would work.
Initcall function names are not available without KALLSYMS. That
dependency would increase kernel size. So "text based" does not
seem too good.
Of course, if you are creating a "text based list" at compile time,
a macro could easily convert an init function text name to the
function pointer that is used in do_initcall_level(). Thus you
would have a not so large list of function pointers.
< snip >
-Frank
prev parent reply other threads:[~2014-10-22 9:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 5:07 Why is the deferred initcall patch not mainline? Dirk Behme
2014-10-18 8:11 ` Bird, Tim
2014-10-18 14:05 ` Alexandre Belloni
2014-10-18 21:09 ` Bird, Tim
2014-10-20 8:32 ` Geert Uytterhoeven
2014-10-19 6:59 ` Dirk Behme
2014-10-21 11:27 ` Alexandre Belloni
2014-10-21 12:52 ` Grant Likely
2014-10-21 12:53 ` Grant Likely
2014-10-21 16:31 ` Nicolas Pitre
2014-10-21 19:37 ` Bird, Tim
2014-10-21 19:58 ` Nicolas Pitre
2014-10-22 10:05 ` Geert Uytterhoeven
2014-10-22 15:05 ` Rob Landley
2014-10-22 15:49 ` Nicolas Pitre
2014-10-23 17:21 ` Bird, Tim
2014-10-23 17:56 ` Nicolas Pitre
2014-10-23 18:13 ` Alexandre Belloni
2014-10-23 19:05 ` Nicolas Pitre
2014-10-23 20:10 ` Bird, Tim
2014-10-23 20:50 ` Nicolas Pitre
2014-10-23 22:37 ` Rob Landley
2014-10-24 0:36 ` Nicolas Pitre
2014-10-24 19:38 ` Rob Landley
2014-10-24 20:28 ` Geert Uytterhoeven
2014-10-27 20:29 ` Nicolas Pitre
2014-10-27 21:37 ` Alexandre Belloni
2014-10-29 23:49 ` Tim Bird
2014-10-30 8:51 ` Geert Uytterhoeven
2014-11-02 2:37 ` Nicolas Pitre
2014-11-02 9:01 ` Geert Uytterhoeven
2014-11-02 3:46 ` Nicolas Pitre
2014-10-24 21:05 ` Nicolas Pitre
2014-10-23 22:01 ` Rob Landley
2014-10-24 0:31 ` Nicolas Pitre
2014-10-23 18:37 ` Rob Landley
2014-10-22 5:31 ` Dirk Behme
2014-10-22 9:49 ` Frank Rowand [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=54477DA3.3040605@gmail.com \
--to=frowand.list@gmail.com \
--cc=Tim.Bird@sonymobile.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=bp@alien8.de \
--cc=dirk.behme@gmail.com \
--cc=geert@linux-m68k.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-embedded@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=tim.bird@am.sony.com \
/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.