- * correct name is being returned if we're not making an
- * entry. In addition for monitored vnodes we need to
- * kick the vnode out of the name cache. We do this so
- * that if there are hard links in the same directory
- * the link will not be found and a lookup will get us
- * here to return the name of the current link. In
- * addition by removing the name from the name cache the
- * old name will not be found after a rename done on
- * another client or the server. The principle reason
- * to do this is because Finder is asking for
- * notifications on a directory. The directory changes,
- * Finder gets notified, reads the directory (which we
- * have purged) and for each entry returned calls
- * getattrlist with the name returned from
- * readdir. gettattrlist has to call namei/lookup to
- * resolve the name, because its not in the cache we end
- * up here. We need to update the name so Finder will
- * get the name it called us with.
+ * correct name is being returned. In addition for
+ * monitored vnodes we need to kick the vnode out of the
+ * name cache. We do this so that if there are hard
+ * links in the same directory the link will not be
+ * found and a lookup will get us here to return the
+ * name of the current link. In addition by removing the
+ * name from the name cache the old name will not be
+ * found after a rename done on another client or the
+ * server. The principle reason to do this is because
+ * Finder is asking for notifications on a directory.
+ * The directory changes, Finder gets notified, reads
+ * the directory (which we have purged) and for each
+ * entry returned calls getattrlist with the name
+ * returned from readdir. gettattrlist has to call
+ * namei/lookup to resolve the name, because its not in
+ * the cache we end up here. We need to update the name
+ * so Finder will get the name it called us with.