Commit 35b21085 authored by Daniel Borkmann's avatar Daniel Borkmann Committed by John Stultz

ktime: Add __must_check prefix to ktime_to_timespec_cond

The function is currently mainly used in the networking code and
if others start using it, they must check the result, otherwise
it cannot be determined if the timespec conversion suceeded.
Currently no user lacks this check, but make future users aware of
a possible misusage.
Signed-off-by: default avatarDaniel Borkmann <dborkman@redhat.com>
Signed-off-by: default avatarJohn Stultz <john.stultz@linaro.org>
parent a44b8bd6
...@@ -339,7 +339,8 @@ extern ktime_t ktime_add_safe(const ktime_t lhs, const ktime_t rhs); ...@@ -339,7 +339,8 @@ extern ktime_t ktime_add_safe(const ktime_t lhs, const ktime_t rhs);
* *
* Returns true if there was a successful conversion, false if kt was 0. * Returns true if there was a successful conversion, false if kt was 0.
*/ */
static inline bool ktime_to_timespec_cond(const ktime_t kt, struct timespec *ts) static inline __must_check bool ktime_to_timespec_cond(const ktime_t kt,
struct timespec *ts)
{ {
if (kt.tv64) { if (kt.tv64) {
*ts = ktime_to_timespec(kt); *ts = ktime_to_timespec(kt);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment