[src/trunk]: src/sys/sys Regen.

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

details:   https://anonhg.NetBSD.org/src/rev/1b0fa367b2b7
branches:  trunk
changeset: 999459:1b0fa367b2b7
user:      msaitoh <msaitoh%NetBSD.org@localhost>
date:      Mon Jun 03 06:05:39 2019 +0000

description:
Regen.

diffstat:

 sys/rump/include/rump/rump_namei.h |  4 ++--
 sys/sys/namei.h                    |  6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diffs (43 lines):

diff -r 1d197b837ea5 -r 1b0fa367b2b7 sys/rump/include/rump/rump_namei.h
--- a/sys/rump/include/rump/rump_namei.h        Mon Jun 03 06:04:20 2019 +0000
+++ b/sys/rump/include/rump/rump_namei.h        Mon Jun 03 06:05:39 2019 +0000
@@ -1,11 +1,11 @@
-/*     $NetBSD: rump_namei.h,v 1.31 2017/03/21 10:20:38 riastradh Exp $        */
+/*     $NetBSD: rump_namei.h,v 1.32 2019/06/03 06:05:39 msaitoh Exp $  */
 
 
 /*
  * WARNING: GENERATED FILE.  DO NOT EDIT
  * (edit namei.src and run make namei in src/sys/sys)
  *   by:   NetBSD: gennameih.awk,v 1.5 2009/12/23 14:17:19 pooka Exp 
- *   from: NetBSD: namei.src,v 1.41 2017/03/21 10:20:12 riastradh Exp 
+ *   from: NetBSD: namei.src,v 1.42 2019/06/03 06:04:21 msaitoh Exp 
  */
 
 #ifndef _RUMP_RUMP_NAMEI_H_
diff -r 1d197b837ea5 -r 1b0fa367b2b7 sys/sys/namei.h
--- a/sys/sys/namei.h   Mon Jun 03 06:04:20 2019 +0000
+++ b/sys/sys/namei.h   Mon Jun 03 06:05:39 2019 +0000
@@ -1,11 +1,11 @@
-/*     $NetBSD: namei.h,v 1.97 2017/03/21 10:20:38 riastradh Exp $     */
+/*     $NetBSD: namei.h,v 1.98 2019/06/03 06:05:39 msaitoh Exp $       */
 
 
 /*
  * WARNING: GENERATED FILE.  DO NOT EDIT
  * (edit namei.src and run make namei in src/sys/sys)
  *   by:   NetBSD: gennameih.awk,v 1.5 2009/12/23 14:17:19 pooka Exp 
- *   from: NetBSD: namei.src,v 1.41 2017/03/21 10:20:12 riastradh Exp 
+ *   from: NetBSD: namei.src,v 1.42 2019/06/03 06:04:21 msaitoh Exp 
  */
 
 /*
@@ -208,7 +208,7 @@
  * Namecache entry.  This structure is arranged so that frequently
  * accessed and mostly read-only data is toward the front, with
  * infrequently accessed data and the lock towards the rear.  The
- * lock is then more likely to be in a seperate cache line.
+ * lock is then more likely to be in a separate cache line.
  *
  * Locking rules:
  *