write in 30M

hc

2024-02-20 ea08eeccae9297f7aabd2ef7f0c2517ac4549acc

 kernel/Documentation/core-api/timekeeping.rst
..
..
@@ -65,7 +65,7 @@
65
65
 .. c:function:: u64 ktime_get_ns( void )
66
66
 		u64 ktime_get_boottime_ns( void )
67
67
 		u64 ktime_get_real_ns( void )
68
-		u64 ktime_get_tai_ns( void )
68
+		u64 ktime_get_clocktai_ns( void )
69
69
 		u64 ktime_get_raw_ns( void )
70
70
 
71
71
 	Same as the plain ktime_get functions, but returning a u64 number
..
..
@@ -115,7 +115,7 @@
115
115
 		void ktime_get_coarse_clocktai_ts64( struct timespec64 * )
116
116
 
117
117
 	These are quicker than the non-coarse versions, but less accurate,
118
-	corresponding to CLOCK_MONONOTNIC_COARSE and CLOCK_REALTIME_COARSE
118
+	corresponding to CLOCK_MONOTONIC_COARSE and CLOCK_REALTIME_COARSE
119
119
 	in user space, along with the equivalent boottime/tai/raw
120
120
 	timebase not available in user space.
121
121
 
..
..
@@ -154,9 +154,9 @@
154
154
 
155
155
 	Use ktime_get() or ktime_get_ts64() instead.
156
156
 
157
-.. c:function:: struct timeval do_gettimeofday( void )
158
-		struct timespec getnstimeofday( void )
159
-		struct timespec64 getnstimeofday64( void )
157
+.. c:function:: void do_gettimeofday( struct timeval * )
158
+		void getnstimeofday( struct timespec * )
159
+		void getnstimeofday64( struct timespec64 * )
160
160
 		void ktime_get_real_ts( struct timespec * )
161
161
 
162
162
 	ktime_get_real_ts64() is a direct replacement, but consider using