summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorrwatson <rwatson@FreeBSD.org>2001-10-27 05:05:39 +0000
committerrwatson <rwatson@FreeBSD.org>2001-10-27 05:05:39 +0000
commitb985eb702b13ce86007aa55c5cb9745aa2161d5c (patch)
tree6a8f51b414c7cdd74c4ff63226a5f02bdec5bcb1
parent1d903fb701690db4513baed9d955b58693c07f38 (diff)
downloadFreeBSD-src-b985eb702b13ce86007aa55c5cb9745aa2161d5c.zip
FreeBSD-src-b985eb702b13ce86007aa55c5cb9745aa2161d5c.tar.gz
o The comment about ordering the destruction of the lock and the removal of
the flag indicating that the structure was initialized didn't need an XXX, since it didn't need fixing. Obtained from: TrustedBSD Project
-rw-r--r--sys/ufs/ufs/ufs_extattr.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/ufs/ufs/ufs_extattr.c b/sys/ufs/ufs/ufs_extattr.c
index e944114..7bbe239 100644
--- a/sys/ufs/ufs/ufs_extattr.c
+++ b/sys/ufs/ufs/ufs_extattr.c
@@ -177,7 +177,7 @@ ufs_extattr_uepm_destroy(struct ufs_extattr_per_mount *uepm)
panic("ufs_extattr_uepm_destroy: called while still started");
/*
- * XXX: It's not clear that either order for the next two lines is
+ * It's not clear that either order for the next two lines is
* ideal, and it should never be a problem if this is only called
* during unmount, and with vfs_busy().
*/
OpenPOWER on IntegriCloud