Searched hist:203968 (Results 1 - 6 of 6) sorted by relevance

/freebsd-10-stable/sys/modules/nfs_common/
H A DMakefile203968 Tue Feb 16 18:00:32 MST 2010 marius Factor out the code shared between NFS client and server into its own
module. With r203732 it became apparent that creating the sysctl nodes
twice causes at least a warning, however the whole code shouldn't be
present twice in the first place.

Discussed with: rmacklem
/freebsd-10-stable/sys/modules/nfsclient/
H A DMakefilediff 203968 Tue Feb 16 18:00:32 MST 2010 marius Factor out the code shared between NFS client and server into its own
module. With r203732 it became apparent that creating the sysctl nodes
twice causes at least a warning, however the whole code shouldn't be
present twice in the first place.

Discussed with: rmacklem
/freebsd-10-stable/sys/modules/nfsserver/
H A DMakefilediff 203968 Tue Feb 16 18:00:32 MST 2010 marius Factor out the code shared between NFS client and server into its own
module. With r203732 it became apparent that creating the sysctl nodes
twice causes at least a warning, however the whole code shouldn't be
present twice in the first place.

Discussed with: rmacklem
/freebsd-10-stable/sys/nfs/
H A Dnfs_common.cdiff 203968 Tue Feb 16 18:00:32 MST 2010 marius Factor out the code shared between NFS client and server into its own
module. With r203732 it became apparent that creating the sysctl nodes
twice causes at least a warning, however the whole code shouldn't be
present twice in the first place.

Discussed with: rmacklem
/freebsd-10-stable/sys/nfsserver/
H A Dnfs_srvsubs.cdiff 203968 Tue Feb 16 18:00:32 MST 2010 marius Factor out the code shared between NFS client and server into its own
module. With r203732 it became apparent that creating the sysctl nodes
twice causes at least a warning, however the whole code shouldn't be
present twice in the first place.

Discussed with: rmacklem
/freebsd-10-stable/sys/nfsclient/
H A Dnfs_vfsops.cdiff 203968 Tue Feb 16 18:00:32 MST 2010 marius Factor out the code shared between NFS client and server into its own
module. With r203732 it became apparent that creating the sysctl nodes
twice causes at least a warning, however the whole code shouldn't be
present twice in the first place.

Discussed with: rmacklem

Completed in 241 milliseconds