07 Feb, 2008

1 commit

  • Mostly trivial conversion with one exceptions: h_num_logops was kept in
    native endian previously and only converted to big endian in xlog_sync,
    but we always keep it big endian now. With todays cpus fast byteswap
    instructions that's not an issue but the new variant keeps the code clean
    and maintainable.

    SGI-PV: 971186
    SGI-Modid: xfs-linux-melb:xfs-kern:29821a

    Signed-off-by: Christoph Hellwig
    Signed-off-by: Lachlan McIlroy
    Signed-off-by: Tim Shimmin

    Christoph Hellwig
     

28 Sep, 2006

1 commit


29 Mar, 2006

1 commit


11 Jan, 2006

1 commit


09 Jan, 2006

1 commit

  • Remove various things which were checking for gcc-1.x and gcc-2.x compilers.

    From: Adrian Bunk

    Some documentation updates and removes some code paths for gcc < 3.2.

    Acked-by: Russell King
    Signed-off-by: Adrian Bunk
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andrew Morton
     

02 Nov, 2005

2 commits

  • boilerplate.

    SGI-PV: 913862
    SGI-Modid: xfs-linux:xfs-kern:23903a

    Signed-off-by: Nathan Scott

    Nathan Scott
     
  • writes. In addition flush the disk cache on fsync if the sync cached
    operation didn't sync the log to disk (this requires some additional
    bookeping in the transaction and log code). If the device doesn't claim to
    support barriers, the filesystem has an extern log volume or the trial
    superblock write with barriers enabled failed we disable barriers and
    print a warning. We should probably fail the mount completely, but that
    could lead to nasty boot failures for the root filesystem. Not enabled by
    default yet, needs more destructive testing first.

    SGI-PV: 912426
    SGI-Modid: xfs-linux:xfs-kern:198723a

    Signed-off-by: Christoph Hellwig
    Signed-off-by: Nathan Scott

    Christoph Hellwig
     

02 Sep, 2005

1 commit


17 Apr, 2005

1 commit

  • 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!

    Linus Torvalds