1. 19 Apr, 2006 1 commit
  2. 18 Nov, 2005 1 commit
  3. 10 Nov, 2005 1 commit
    • Laurent riffard's avatar
      [PATCH] PCI: automatically set device_driver.owner · 863b18f4
      Laurent riffard authored
      A nice feature of sysfs is that it can create the symlink from the
      driver to the module that is contained in it.
      It requires that the device_driver.owner is set, what is not the
      case for many PCI drivers.
      This patch allows pci_register_driver to set automatically the
      device_driver.owner for any PCI driver.
      Credits to Al Viro who suggested the method.
      Signed-off-by: default avatarLaurent Riffard <laurent.riffard@free.fr>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
       drivers/ide/setup-pci.c  |   12 +++++++-----
       drivers/pci/pci-driver.c |    9 +++++----
       include/linux/ide.h      |    3 ++-
       include/linux/pci.h      |   10 ++++++++--
       4 files changed, 22 insertions(+), 12 deletions(-)
  4. 18 Aug, 2005 1 commit
  5. 01 Jul, 2005 1 commit
    • Greg Kroah-Hartman's avatar
      [PATCH] PCI: clean up dynamic pci id logic · 75865858
      Greg Kroah-Hartman authored
      The dynamic pci id logic has been bothering me for a while, and now that
      I started to look into how to move some of this to the driver core, I
      thought it was time to clean it all up.
      It ends up making the code smaller, and easier to follow, and fixes a
      few bugs at the same time (dynamic ids were not being matched
      everywhere, and so could be missed on some call paths for new devices,
      semaphore not needed to be grabbed when adding a new id and calling the
      driver core, etc.)
      I also renamed the function pci_match_device() to pci_match_id() as
      that's what it really does.
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
  6. 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!