diff --git a/auth2-pam.c b/auth2-pam.c
index 79bd4a813..490921d84 100644
--- a/auth2-pam.c
+++ b/auth2-pam.c
@@ -1,5 +1,5 @@
 #include "includes.h"
-RCSID("$Id: auth2-pam.c,v 1.9 2001/02/15 00:51:32 djm Exp $");
+RCSID("$Id: auth2-pam.c,v 1.10 2001/02/16 02:03:04 djm Exp $");
 
 #ifdef USE_PAM
 #include <security/pam_appl.h>
@@ -107,10 +107,12 @@ do_pam_conversation_kbd_int(int num_msg, const struct pam_message **msg,
 	packet_send();
 	packet_write_wait();
 
-	/* Grabbing control of execution and spinning until we get what
+	/*
+	 * Grabbing control of execution and spinning until we get what
 	 * we want is probably rude, but it seems to work properly, and
 	 * the client *should* be in lock-step with us, so the loop should
-	 * only be traversed once. */
+	 * only be traversed once.
+	 */
 	while(context_pam2.finished == 0) {
 		done = 1;
 		dispatch_run(DISPATCH_BLOCK, &done, appdata_ptr);