Don't truncate Ktime to milliseconds #136
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sharlns
force-pushed
the
fix_ktime_millisec
branch
from
62d4ada to
5d371eb
Compare
|
the change itself looks good to me. could you update the commit message to something like: also, you don't need to change it for this pr, but in general use |
Report event timestamp in nanoseconds to give a higher resolution. Fixes #124 Signed-off-by: Natalia Reka Ivanko <[email protected]>
sharlns
force-pushed
the
fix_ktime_millisec
branch
from
5d371eb to
c86deff
Compare
michi-covalent
approved these changes
Jun 8, 2022
willfindlay
approved these changes
Jun 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Don't truncate Ktime to milliseconds and give a higher resolution. Fix for #124.