Trivial improvement to comments
This commit is contained in:
parent
72bd1e7634
commit
b04e2ea021
@ -1 +1 @@
|
||||
Subproject commit f080d80b68c7f98694ab9db8fad0e4d27e2436d7
|
||||
Subproject commit b4f9bbd9708111b44d40ff19248b5493fdafc6c1
|
2
configs
2
configs
@ -1 +1 @@
|
||||
Subproject commit 6789354447c099458909b61fd03bbec045f03eed
|
||||
Subproject commit d9bb7ac167d730a1c152cea388852c8690795d93
|
@ -138,7 +138,10 @@ int clock_systimespec(FAR struct timespec *ts)
|
||||
uint64_t secs;
|
||||
uint64_t nsecs;
|
||||
|
||||
/* Get the time since power-on in seconds and microsecon */
|
||||
/* Get the time since power-on in seconds and microsecond.
|
||||
* NOTE that overflow is still possible if we use a 64-bit
|
||||
* timer.
|
||||
*/
|
||||
|
||||
usecs = (uint64_t)TICK2USEC(clock_systimer());
|
||||
secs = usecs / USEC_PER_SEC;
|
||||
@ -161,7 +164,7 @@ int clock_systimespec(FAR struct timespec *ts)
|
||||
* of 10 milliseconds, the msecs value will overflow at about
|
||||
* 49.7 days.
|
||||
*
|
||||
* So, we will still use 64-bit calculations if we have them
|
||||
* So.. we will still use 64-bit calculations if we have them
|
||||
* in order to avoid that limitation.
|
||||
*/
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user