1. 07 1月, 2011 5 次提交
  2. 10 2月, 2010 1 次提交
  3. 06 12月, 2009 2 次提交
  4. 18 6月, 2009 10 次提交
  5. 29 3月, 2009 1 次提交
    • C
      NFS: Start PF_INET6 callback listener only if IPv6 support is available · f738f517
      Chuck Lever 提交于
      Apparently a lot of people need to disable IPv6 completely on their
      distributor-built systems, which have CONFIG_IPV6_MODULE enabled at
      build time.
      
      They do this by blacklisting the ipv6.ko module.  This causes the
      creation of the NFSv4 callback service listener to fail if
      CONFIG_IPV6_MODULE is set, but the module cannot be loaded.
      
      Now that the kernel's PF_INET6 RPC listeners are completely separate
      from PF_INET listeners, we can always start PF_INET.  Then the NFS
      client can try to start a PF_INET6 listener, but it isn't required
      to be available.
      Signed-off-by: NChuck Lever <chuck.lever@oracle.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      f738f517
  6. 30 1月, 2008 2 次提交
  7. 15 5月, 2007 1 次提交
    • T
      NFS: Fix more sparse warnings · 2e42c3e2
      Trond Myklebust 提交于
       - fs/nfs/nfs4xdr.c:2499:42: warning: incorrect type in argument 2
         (different signedness)
       - fs/nfs/nfs4xdr.c:2658:49: warning: incorrect type in argument 4
         (different explicit signedness)
       - fs/nfs/nfs4xdr.c:2683:50: warning: incorrect type in argument 4
         (different explicit signedness)
       - fs/nfs/nfs4xdr.c:3063:68: warning: incorrect type in argument 4
         (different explicit signedness)
       - fs/nfs/nfs4xdr.c:3065:68: warning: incorrect type in argument 4
         (different explicit signedness)
      
       - fs/nfs/callback_xdr.c:138:31: warning: incorrect type in argument 2
         (different signedness)
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      2e42c3e2
  8. 21 10月, 2006 2 次提交
  9. 23 9月, 2006 1 次提交
  10. 07 1月, 2006 1 次提交
  11. 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