1. 24 3月, 2006 1 次提交
    • N
      [PATCH] Make libata not powerdown drivers on PM_EVENT_FREEZE. · 082776e4
      Nigel Cunningham 提交于
      At the moment libata doesn't pass pm_message_t down ata_device_suspend.
      This causes drives to be powered down when we just want a freeze,
      causing unnecessary wear and tear. This patch gets pm_message_t passed
      down so that it can be used to determine whether to power down the
      drive.
      Signed-off-by: NNigel Cunningham <nigel@suspend2.net>
      
       drivers/scsi/libata-core.c |    5 +++--
       drivers/scsi/libata-scsi.c |    4 ++--
       drivers/scsi/scsi_sysfs.c  |    2 +-
       include/linux/libata.h     |    4 ++--
       include/scsi/scsi_host.h   |    2 +-
       5 files changed, 9 insertions(+), 8 deletions(-)
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      082776e4
  2. 13 3月, 2006 1 次提交
  3. 25 1月, 2006 1 次提交
  4. 13 1月, 2006 1 次提交
  5. 07 1月, 2006 1 次提交
    • J
      [PATCH] Suspend support for libata · 9b847548
      Jens Axboe 提交于
      This patch adds suspend patch to libata, and ata_piix in particular. For
      most low level drivers, they should just need to add the 4 hooks to
      work. As I can only test ata_piix, I didn't enable it for more
      though.
      
      Suspend support is the single most important feature on a notebook, and
      most new notebooks have sata drives. It's quite embarrassing that we
      _still_ do not support this. Right now, it's perfectly possible to
      suspend the drive in mid-transfer.
      Signed-off-by: NJens Axboe <axboe@suse.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9b847548
  6. 06 1月, 2006 1 次提交
  7. 07 11月, 2005 2 次提交
  8. 29 10月, 2005 2 次提交
  9. 19 9月, 2005 2 次提交
  10. 07 9月, 2005 1 次提交
  11. 31 7月, 2005 3 次提交
  12. 26 6月, 2005 1 次提交
  13. 26 5月, 2005 1 次提交
  14. 19 4月, 2005 1 次提交
  15. 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