1. 20 5月, 2008 1 次提交
  2. 29 1月, 2008 1 次提交
  3. 13 10月, 2007 1 次提交
    • S
      kconfig: fix segv fault in menuconfig · a67cb131
      Sam Ravnborg 提交于
      With specific configurations requesting help for certain
      menu lines caused menuconfig to crash.
      This was tracked down to a null pointer bug.
      Thanks to "Miles Lane" <miles.lane@gmail.com> for inital reporting
      and to Gabriel C <nix.or.die@googlemail.com> for the backtrace
      that helped me locating the bug.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      a67cb131
  4. 09 6月, 2006 1 次提交
    • R
      kconfig: fix .config dependencies · c955ccaf
      Roman Zippel 提交于
      This fixes one of the worst kbuild warts left - the broken dependencies used
      to check and regenerate the .config file.  This was done via an indirect
      dependency and the .config itself had an empty command, which can cause make
      not to reread the changed .config file.
      
      Instead of this we generate now a new file include/config/auto.conf from
      .config, which is used for kbuild and has the proper dependencies.  It's also
      the main make target now for all files generated during this step (and thus
      replaces include/linux/autoconf.h).
      
      This also means we can now relax the syntax requirements for the .config file
      and we don't have to rewrite it all the time, i.e.  silentoldconfig only
      writes .config now when it's necessary to keep it in sync with the Kconfig
      files and even this can be suppressed by setting the environment variable
      KCONFIG_NOSILENTUPDATE, so the update can (and must) be done manually.
      Signed-off-by: NRoman Zippel <zippel@linux-m68k.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      c955ccaf
  5. 03 1月, 2006 1 次提交
  6. 27 12月, 2005 1 次提交
  7. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4