1. 28 4月, 2007 1 次提交
  2. 17 2月, 2007 1 次提交
  3. 08 2月, 2007 2 次提交
  4. 02 12月, 2006 1 次提交
  5. 28 9月, 2006 2 次提交
  6. 21 3月, 2006 1 次提交
  7. 05 1月, 2006 2 次提交
    • A
      [PATCH] USB: mark various usb tables const · 4c4c9432
      Arjan van de Ven 提交于
      patch below marks various USB tables and variables as const so that they
      end up in .rodata section and don't cacheline share with things that get
      written to. For the non-array variables it also allows gcc to optimize
      more.
      Signed-off-by: NArjan van de Ven <arjan@infradead.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      4c4c9432
    • A
      [PATCH] USB: Remove USB private semaphore · 9ad3d6cc
      Alan Stern 提交于
      This patch (as605) removes the private udev->serialize semaphore,
      relying instead on the locking provided by the embedded struct device's
      semaphore.  The changes are confined to the core, except that the
      usb_trylock_device routine now uses the return convention of
      down_trylock rather than down_read_trylock (they return opposite values
      for no good reason).
      
      A couple of other associated changes are included as well:
      
      	Now that we aren't concerned about HCDs that avoid using the
      	hcd glue layer, usb_disconnect no longer needs to acquire the
      	usb_bus_lock -- that can be done by usb_remove_hcd where it
      	belongs.
      
      	Devices aren't locked over the same scope of code in
      	usb_new_device and hub_port_connect_change as they used to be.
      	This shouldn't cause any trouble.
      
      Along with the preceding driver core patch, this needs a lot of testing.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      9ad3d6cc
  8. 21 6月, 2005 1 次提交
  9. 19 4月, 2005 2 次提交
  10. 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