Revision 62e4a76987eab2b7fa952546614bc83e5bfc9d3e authored by Trond Myklebust on 10 November 2011, 19:30:37 UTC, committed by Trond Myklebust on 10 November 2011, 19:50:26 UTC
pNFS-specific code belongs in the pnfs layer. It should not be hijacking generic NFS read or write code paths. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
1 parent 2aa1353
File | Mode | Size |
---|---|---|
CodingStyle | -rw-r--r-- | 29.1 KB |
HOWTO | -rw-r--r-- | 27.2 KB |
SecurityBugs | -rw-r--r-- | 2.7 KB |
SubmittingDrivers | -rw-r--r-- | 7.5 KB |
SubmittingPatches | -rw-r--r-- | 19.1 KB |
email-clients.txt | -rw-r--r-- | 9.3 KB |
magic-number.txt | -rw-r--r-- | 10.6 KB |
oops-tracing.txt | -rw-r--r-- | 11.3 KB |
sparse.txt | -rw-r--r-- | 3.8 KB |
stable_api_nonsense.txt | -rw-r--r-- | 9.6 KB |
stable_kernel_rules.txt | -rw-r--r-- | 3.7 KB |
volatile-considered-harmful.txt | -rw-r--r-- | 6.4 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...