Skip to content
  1. Jul 22, 2010
  2. Jul 12, 2010
  3. Jul 07, 2010
  4. Jul 05, 2010
  5. Jun 30, 2010
  6. Jun 18, 2010
    • Michal Marek's avatar
      kbuild: Clean up and speed up the localversion logic · 09155120
      Michal Marek authored
      
      
      Now that we run scripts/setlocalversion during every build, it makes
      sense to move all the localversion logic there. This cleans up the
      toplevel Makefile and also makes sure that the script is called only
      once in 'make prepare' (previously, it would be called every time due to
      a variable expansion in an ifneq statement). No user-visible change is
      intended, unless one runs the setlocalversion script directly.
      
      Reported-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      Cc: David Rientjes <rientjes@google.com>
      Cc: Greg Thelen <gthelen@google.com>
      Cc: Nico Schottelius <nico-linuxsetlocalversion@schottelius.org>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      09155120
  7. Jun 15, 2010
    • Andy Whitcroft's avatar
      kbuild: fix LOCALVERSION handling to match description · d5eda75f
      Andy Whitcroft authored
      
      
      In the commit below the version string handling was modified, adding
      a '+' where no other version information was supplied:
      
          commit 85a256d8
          Author: David Rientjes <rientjes@google.com>
          Date:   Wed Jan 13 13:01:05 2010 -0800
      
      From the commit the intent was as below:
      
           - when CONFIG_LOCALVERSION_AUTO is disabled, a `+' is appended if the
             repository has been revised beyond a tagged commit and LOCALVERSION=
             was not passed to "make".
      
      However if the user supplies an empty LOCALVERSION on the command line
      the plus suffix is still added.  This form is useful in the case where
      the build environment knows that the version as specified is correct and
      complete but does not correspond to a specific tag.
      
      This patch changes the implementation to match the documentation
      such that specifying LOCALVERSION= on the build line is sufficient
      to suppress any suffix.
      
      Signed-off-by: default avatarAndy Whitcroft <apw@canonical.com>
      Acked-by: default avatarDavid Rientjes <rientjes@google.com>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      d5eda75f
  8. Jun 12, 2010
  9. Jun 09, 2010
  10. Jun 06, 2010
  11. May 30, 2010
  12. May 16, 2010
  13. May 10, 2010
  14. May 06, 2010
  15. Apr 30, 2010
  16. Apr 19, 2010
  17. Apr 13, 2010
  18. Mar 30, 2010
  19. Mar 20, 2010
  20. Mar 10, 2010
  21. Mar 08, 2010
  22. Feb 24, 2010
  23. Feb 12, 2010
  24. Feb 06, 2010
  25. Feb 05, 2010
  26. Feb 02, 2010
    • Joe Perches's avatar
    • David Rientjes's avatar
      kbuild: improve version string logic · 85a256d8
      David Rientjes authored
      
      
      The LOCALVERSION= string passed to "make" will now always be appended to
      the kernel version after CONFIG_LOCALVERSION, if it exists, regardless of
      whether CONFIG_LOCALVERSION_AUTO is set or not.  This allows users to
      uniquely identify their kernel builds with a string.
      
      If CONFIG_LOCALVERSION_AUTO is enabled, the unique SCM tag reported by
      setlocalversion (or .scmversion) is appended to the kernel version, if it
      exists.  When CONFIG_LOCALVERSION_AUTO is not enabled, a `+' is appended
      to the kernel version to represent that the kernel has been revised since
      the last release unless "make LOCALVERSION=" was used to uniquely identify
      the build.
      
      The end result is this:
      
       - when LOCALVERSION= is passed to "make", it is appended to the kernel
         version,
      
       - when CONFIG_LOCALVERSION_AUTO is enabled, a unique SCM identifier is
         appended if the respository has been revised beyond a tagged commit,
         and
      
       - when CONFIG_LOCALVERSION_AUTO is disabled, a `+' is appended if the
         repository has been revised beyond a tagged commit and LOCALVERSION=
         was not passed to "make".
      
      Examples:
      
      With CONFIG_LOCALVERSION_AUTO: "make" results in
      v2.6.32-rc4-00149-ga3ccf63.  If there are uncommited changes to the
      respository, it results in v2.6.32-rc4-00149-ga3ccf63-dirty.  If
      "make LOCALVERSION=kbuild" were used, it results in
      v2.6.32-rc4-kbuild-00149-ga3ccf63-dirty.
      
      Without CONFIG_LOCALVERSION_AUTO, "make" results in v2.6.32-rc4+
      unless the repository is at the Linux v2.6.32-rc4 commit (in which
      case the version would be v2.6.32-rc4).  If "make LOCALVERSION=kbuild"
      were used, it results in v2.6.32-rc4-kbuild.
      
      Also renames variables such as localver-auto and _localver-auto to more
      accurately describe what they represent: localver-extra and
      scm-identifier, respectively.
      
      Signed-off-by: default avatarDavid Rientjes <rientjes@google.com>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      85a256d8
    • Roland McGrath's avatar
      kconfig CROSS_COMPILE option · 84336466
      Roland McGrath authored
      
      
      This adds CROSS_COMPILE as a kconfig string so you can store it in
      .config.  Then you can use plain "make" in the configured kernel build
      directory to do the right cross compilation without setting the
      command-line or environment variable every time.
      
      With this, you can set up different build directories for different kernel
      configurations, whether native or cross-builds, and then use the simple:
      
      	make -C /build/dir M=module-source-dir
      
      idiom to build modules for any given target kernel, indicating which one
      by nothing but the build directory chosen.
      
      I tried a version that defaults the string with env="CROSS_COMPILE" so
      that in a "make oldconfig" with CROSS_COMPILE in the environment you can
      just hit return to store the way you're building it.  But the kconfig
      prompt for strings doesn't give you any way to say you want an empty
      string instead of the default, so I punted that.
      
      Signed-off-by: default avatarRoland McGrath <roland@redhat.com>
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Cc: Anibal Monsalve Salazar <anibal@debian.org>
      Cc: Steven Rostedt <rostedt@goodmis.org>
      Cc: Michal Marek <mmarek@suse.cz>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarMichal Marek <mmarek@suse.cz>
      84336466
  27. Jan 29, 2010
  28. Jan 21, 2010
  29. Jan 13, 2010
  30. Jan 06, 2010
  31. Dec 24, 2009
  32. Dec 18, 2009
  33. Dec 17, 2009
  34. Dec 12, 2009
Loading