[src/trunk]: src/sys/arch/x86/x86 leading whitespace too!

[jakllsch <jakllsch%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/468f90d73847
branches:  trunk
changeset: 772801:468f90d73847
user:      jakllsch <jakllsch%NetBSD.org@localhost>
date:      Tue Jan 17 03:06:33 2012 +0000

description:
leading whitespace too!

diffstat:

 sys/arch/x86/x86/via_padlock.c |  6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diffs (28 lines):

diff -r 3027888ba304 -r 468f90d73847 sys/arch/x86/x86/via_padlock.c
--- a/sys/arch/x86/x86/via_padlock.c    Tue Jan 17 03:01:39 2012 +0000
+++ b/sys/arch/x86/x86/via_padlock.c    Tue Jan 17 03:06:33 2012 +0000
@@ -1,5 +1,5 @@
 /*     $OpenBSD: via.c,v 1.8 2006/11/17 07:47:56 tom Exp $     */
-/*     $NetBSD: via_padlock.c,v 1.18 2012/01/17 03:01:39 jakllsch Exp $ */
+/*     $NetBSD: via_padlock.c,v 1.19 2012/01/17 03:06:33 jakllsch Exp $ */
 
 /*-
  * Copyright (c) 2003 Jason Wright
@@ -20,7 +20,7 @@
  */
 
 #include <sys/cdefs.h>
-__KERNEL_RCSID(0, "$NetBSD: via_padlock.c,v 1.18 2012/01/17 03:01:39 jakllsch Exp $");
+__KERNEL_RCSID(0, "$NetBSD: via_padlock.c,v 1.19 2012/01/17 03:06:33 jakllsch Exp $");
 
 #ifdef _KERNEL_OPT
 # include "rnd.h"
@@ -93,7 +93,7 @@
         * registers, which are really for the FPU, in order to read
         * from the RNG.
         *
-        * Don't remove CR0_TS from the call below -- comments in the Linux
+        * Don't remove CR0_TS from the call below -- comments in the Linux
         * driver indicate that the xstorerng instruction can generate
         * spurious DNA faults though no FPU or SIMD state is changed
         * even if such a fault is generated.