Jere Leppänen
Jere Leppänen
This would be nice. But I would suggest adding the following, for compatibility: ``` #define LIBCLI_VERISON_MINOR LIBCLI_VERSION_MINOR #define LIBCLI_VERISON_REVISION LIBCLI_VERSION_REVISION ```
Looks good, but would you be willing to do the same also for pktio_test_chksum_in_ipv4?
I'm not a huge fan of the word myself, but should we use "canary" instead of "endmark"? https://en.wikipedia.org/wiki/Buffer_overflow_protection#Canaries
> Perhaps a more stringent CLI input validation could be considered if this is now becoming a proper tester No more proper than it already was. I don't think we...
v2: - Fixed string.h doxygen comments.
v3: - Rebase. - Add review tags.
v2: Add commit "api: timer: add periodic.max_tmo_events in timer capability".
All comments processed in v2.
v4: - Use acquire and relese semantics on is_idle. - Reorder commits. - Minor tweaking of some commit comments. - Add review tags.
I took the liberty of updating this PR with all the comments processed, commit comments cleaned up a bit, and a couple of new warnings fixed (ML).