1. 13 12月, 2005 1 次提交
  2. 04 12月, 2005 1 次提交
  3. 30 11月, 2005 2 次提交
  4. 18 11月, 2005 1 次提交
    • S
      [CIFS] Vectored and async i/o turned on and correct the · 87c89dd7
      Steve French 提交于
      writev and aio_write to flush properly.
      
      This is Christoph's patch merged with the new nobrl file operations
      Signed-off-by: NDave Kleikamp <shaggy@austin.ibm.com>
      
      From: Christoph Hellwig <hch@lst.de>
      
       - support vectored and async aio ops unconditionally - this is above
         the pagecache and transparent to the fs
       - remove cifs_read_wrapper.  it was only doing silly checks and
         calling generic_file_write in all cases.
       - use do_sync_read/do_sync_write as read/write operations.  They call
         ->readv/->writev which we now always implemente.
       - add the filemap_fdatawrite calls to writev/aio_write which were
         missing previously compared to plain write.  no idea what the point
         behind them is, but let's be consistent at least..
      Signed-off-by: NChristoph Hellwig <hch@lst.de>
      Signed-off-by: NSteven French <sfrench@us.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      87c89dd7
  5. 12 11月, 2005 1 次提交
  6. 10 11月, 2005 1 次提交
  7. 11 10月, 2005 5 次提交
  8. 24 9月, 2005 1 次提交
  9. 22 9月, 2005 1 次提交
  10. 21 9月, 2005 1 次提交
  11. 31 8月, 2005 1 次提交
    • S
      [CIFS] Add support for suspend · 16abbecd
      Steve French 提交于
      cifsd had been preventing software suspend from completing.
      
      Signed-off-by: pavel@suse.de
      Signed-off-by: Steve French <sfrench@us.ibm.com>  lightly modified
      ---
      
       fs/cifs/CHANGES   |    3 ++-
       fs/cifs/cifsfs.c  |    4 ++++
       fs/cifs/connect.c |    2 ++
       3 files changed, 8 insertions(+), 1 deletions(-)
      16abbecd
  12. 19 8月, 2005 2 次提交
  13. 29 4月, 2005 5 次提交
  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