From: Perry Ruiter Date: Tue, 22 Oct 2013 12:46:10 +0000 (-0700) Subject: afs: Clarify comment X-Git-Tag: upstream/1.8.0_pre1^2~962 X-Git-Url: https://git.michaelhowe.org/gitweb/?a=commitdiff_plain;h=f7c31f865cd6cda9105a362f26fdd82a500adb37;p=packages%2Fo%2Fopenafs.git afs: Clarify comment Fixing a couple typos and rewording a comment for clarity in afs_segments.c Change-Id: Ic631b6f8d59e4e9a56f61e583a8ef0f8f8794d8b Reviewed-on: http://gerrit.openafs.org/10364 Reviewed-by: Mark Vitale Tested-by: BuildBot Reviewed-by: Derrick Brashear --- diff --git a/src/afs/afs_segments.c b/src/afs/afs_segments.c index db75daae7..9efcae325 100644 --- a/src/afs/afs_segments.c +++ b/src/afs/afs_segments.c @@ -545,7 +545,7 @@ afs_InvalidateAllSegments(struct vcache *avc) * invalidate all of the relevant chunks. Otherwise, the chunks * will be left with the 'new' data that was never successfully * written to the server, but the DV in the dcache is still the - * old DV. So, we may indefintely serve serve applications data + * old DV. So, we may indefinitely serve data to applications * that is not actually in the file on the fileserver. If we * cannot afs_GetValidDSlot the appropriate entries, currently * there is no way to ensure the dcache is invalidated. So for