1. 28 2月, 2012 1 次提交
  2. 31 7月, 2010 1 次提交
  3. 15 9月, 2009 1 次提交
  4. 20 3月, 2009 1 次提交
  5. 24 10月, 2008 2 次提交
  6. 21 4月, 2008 1 次提交
  7. 05 3月, 2008 1 次提交
    • S
      PCI: fix section mismatch warning in pci_scan_child_bus · 0ab2b57f
      Sam Ravnborg 提交于
      Fix following warning:
      WARNING: vmlinux.o(.text+0x47bdb1): Section mismatch in reference from the function pci_scan_child_bus() to the function .devinit.text:pcibios_fixup_bus()
      
      We had plenty of functions that could be annotated __devinit but due to
      the former restriction that exported symbols could not be annotated
      they were not so.  So annotate these function and fix the references
      from the pci/hotplug/* code to silence the resuting warnings.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      0ab2b57f
  8. 20 6月, 2006 1 次提交
  9. 24 3月, 2006 1 次提交
    • K
      [PATCH] PCI Hotplug: add common acpi functions to core · 783c49fc
      Kristen Accardi 提交于
      shpchprm_acpi.c and pciehprm_acpi.c are nearly identical.  In addition,
      there are functions in both these files that are also in acpiphp_glue.c.
      This patch will remove duplicate functions from shpchp, pciehp, and
      acpiphp and move this functionality to pci_hotplug, as it is not
      hardware specific.  Get rid of shpchprm* and pciehprm* files since they
      are no longer needed.  shpchprm_nonacpi.c and pciehprm_nonacpi.c are
      identical, as well as shpchprm_legacy.c and can be replaced with a
      macro.
      
      This patch also changes acpiphp to use the common hpp code.
      Signed-off-by: NKristen Carlson Accardi <kristen.c.accardi@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      783c49fc
  10. 10 1月, 2006 1 次提交
  11. 11 11月, 2005 1 次提交
  12. 29 10月, 2005 5 次提交
  13. 17 8月, 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