1. 27 5月, 2006 1 次提交
  2. 03 4月, 2006 13 次提交
  3. 12 3月, 2006 1 次提交
  4. 15 1月, 2006 1 次提交
  5. 21 12月, 2005 2 次提交
  6. 09 11月, 2005 1 次提交
    • O
      [PATCH] changing CONFIG_LOCALVERSION rebuilds too much, for no good reason · 733482e4
      Olaf Hering 提交于
      This patch removes almost all inclusions of linux/version.h.  The 3
      #defines are unused in most of the touched files.
      
      A few drivers use the simple KERNEL_VERSION(a,b,c) macro, which is
      unfortunatly in linux/version.h.
      
      There are also lots of #ifdef for long obsolete kernels, this was not
      touched.  In a few places, the linux/version.h include was move to where
      the LINUX_VERSION_CODE was used.
      
      quilt vi `find * -type f -name "*.[ch]"|xargs grep -El '(UTS_RELEASE|LINUX_VERSION_CODE|KERNEL_VERSION|linux/version.h)'|grep -Ev '(/(boot|coda|drm)/|~$)'`
      
      search pattern:
      /UTS_RELEASE\|LINUX_VERSION_CODE\|KERNEL_VERSION\|linux\/\(utsname\|version\).h
      Signed-off-by: NOlaf Hering <olh@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      733482e4
  7. 07 11月, 2005 2 次提交
  8. 29 9月, 2005 1 次提交
  9. 10 9月, 2005 1 次提交
  10. 16 8月, 2005 1 次提交
  11. 22 6月, 2005 4 次提交
  12. 29 5月, 2005 1 次提交
    • P
      [PATCH] intelfb section fix · 346e399b
      Patrick McManus 提交于
      On Nov 16 2004 a change to intelfbdrv.c was commited (as part of 0.9.2 it
      looks like) that added __initdata to all of the module param variables that
      seems to create the opportunity for an oops.
      
      I've recently been chasing an OOPS
      (http://marc.theaimsgroup.com/?l=linux-kernel&m=111552250920370&w=2) I
      created by reading every file on the /sys file system and I've traced it
      back to this code in the intelfbdrv.  Though I had root privs in my initial
      problem report, it turns out they are un-necessary to generate the oops -
      all you've got to do is "cat /sys/module/intelfb/parameters/mode" enough
      times and eventually it will oops.
      
      This is because sysfs automatically exports all module_param declarations
      to the sysfs file system..  which means those variables can be dynamically
      evaluated at any later time, which of course means marking them __initdata
      is a bad idea ;)..  when they happen to be char *'s it is an especially bad
      idea ;).
      
      Applying the patch below clears up the OOPS for me.
      Signed-off-by: NPatrick McManus <mcmanus@ducksong.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      346e399b
  13. 01 5月, 2005 1 次提交
  14. 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