lkml.org 
[lkml]   [2002]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] Initcall depends
    On Sun, 16 Jun 2002 20:17:44 -0500 (CDT)
    Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de> wrote:
    > As you're taking the effort of running some code to figure out the right
    > ordering anyway, have you considered using the the information which is
    > already there today, for all code which can be compiled modular.

    Unfortunately, this is rather painful:

    1) File A contains an initcall.
    2) Find Module A which File A is part of.
    3) For each exported symbol used by Module A
    4) Find Module B which exports this symbol.
    5) Find Files B which make up Module B.
    6) For each initcall in Files B, insert a dependency.

    Any clues for (2) and (5)?
    Rusty.
    --
    there are those who do and those who hang on and you don't see too
    many doers quoting their contemporaries. -- Larry McVoy
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:26    [W:2.564 / U:0.032 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site