1. 22 6月, 2005 1 次提交
    • A
      [PATCH] intelfbdrv naming fix · 5a3b5899
      Andrew Morton 提交于
      Can't use this fancy name, because it's used to generate a sysfs filename:
      
      kobject_register failed for Intel(R) 830M/845G/852GM/855GM/865G/915G
       Framebuffer Driver (-13)
        [<c01bf8e3>] kobject_register+0x43/0x70
        [<c022dfe2>] bus_add_driver+0x52/0xa0
        [<c01c8c10>] pci_device_shutdown+0x0/0x20
        [<c01c8d71>] pci_register_driver+0x61/0x80
        [<c0387099>] intelfb_init+0x59/0x70
        [<c03787cc>] do_initcalls+0x2c/0xc0
        [<c0159025>] kern_mount+0x15/0x17
        [<c01002a0>] init+0x0/0x100
        [<c01002ca>] init+0x2a/0x100
        [<c0100f58>] kernel_thread_helper+0x0/0x18
        [<c0100f5d>] kernel_thread_helper+0x5/0x18
      
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      5a3b5899
  2. 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
  3. 01 5月, 2005 1 次提交
  4. 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