1. 10 Oct, 2008 2 commits
    • Bjorn Helgaas's avatar
      PNP: remove old CONFIG_PNP_DEBUG option · ac88a8f3
      Bjorn Helgaas authored
      CONFIG_PNP_DEBUG is no longer used to turn on dev_dbg() in PNP,
      since we have pnp_dbg() which can be enabled at boot-time, so
      this patch removes the config option.
      
      Note that pnp_dock_event() checks "#ifdef DEBUG".  But there's
      never been a clear path for enabling that via configgery.  It
      happened that CONFIG_PNP_DEBUG enabled it after 1bd17e63
      
      ,
      but that was accidental and only in 2.6.26.
      Signed-off-by: default avatarBjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: default avatarAndi Kleen <ak@linux.intel.com>
      Signed-off-by: default avatarLen Brown <len.brown@intel.com>
      ac88a8f3
    • Linus Torvalds's avatar
      PnP: move pnpacpi/pnpbios_init to after PCI init · ed458df4
      Linus Torvalds authored
      
      We already did that a long time ago for pnp_system_init, but
      pnpacpi_init and pnpbios_init remained as subsys_initcalls, and get
      linked into the kernel before the arch-specific routines that finalize
      the PCI resources (pci_subsys_init).
      
      This means that the PnP routines would either register their resources
      before the PCI layer could, or would be unable to check whether a PCI
      resource had already been registered.  Both are problematic.
      
      I wanted to do this before 2.6.27, but every time we change something
      like this, something breaks.  That said, _every_ single time we trust
      some firmware (like PnP tables) more than we trust the hardware itself
      (like PCI probing), the problems have been worse.
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      ed458df4
  2. 17 Oct, 2007 1 commit
  3. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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