1. 19 Feb, 2006 4 commits
    • Sam Ravnborg's avatar
      kbuild: improved modversioning support for external modules · 040fcc81
      Sam Ravnborg authored
      With following patch a second option is enabled to obtain
      symbol information from a second external module when a
      external module is build.
      The recommended approach is to use a common kbuild file but
      that may be impractical in certain cases.
      With this patch one can copy over a Module.symvers from one
      external module to make symbols (and symbol versions) available
      for another external module.
      
      Updated documentation in Documentation/kbuild/modules.txt
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      040fcc81
    • Sam Ravnborg's avatar
      kbuild: apply CodingStyle to modpost.c · 5c3ead8c
      Sam Ravnborg authored
      Just some light CodingStyle updates - no functional changes.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      5c3ead8c
    • Sam Ravnborg's avatar
      kbuild: use warn()/fatal() consistent in modpost · cb80514d
      Sam Ravnborg authored
      modpost.c provides warn() and fatal() - so use them all over the place.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      cb80514d
    • Sam Ravnborg's avatar
      kbuild: support building individual files for external modules · 06300b21
      Sam Ravnborg authored
      Support building individual files when dealing with separate modules.
      So say you have a module named "foo" which consist of two .o files bar.o
      and fun.o.
      
      You can then do:
      make -C $KERNELSRC M=`pwd` bar.o
      make -C $KERNELSRC M=`pwd` bar.lst
      make -C $KERNELSRC M=`pwd` bar.i
      make -C $KERNELSRC M=`pwd` /            <= will build all .o files
                                                 and link foo.o
      make -C $KERNELSRC M=`pwd` foo.ko       <= will build the module
                                                 and do the modpost step
      					   to create foo.ko
      
      The above will also work if the external module is placed in a
      subdirectory using a hirachy of kbuild files.
      Thanks to Andreas Gruenbacher <agruen@suse.de> for initial feature
      request / bug report.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      06300b21
  2. 17 Feb, 2006 36 commits