Skip to content

Conversation

@andyross
Copy link
Contributor

There were two spots where CONFIG_TIMEOUT_64BIT wasn't being correctly
honored, leading to the possibility of long timeouts overflowing
internally and doing weird stuff.

Fixes #26248

Signed-off-by: Andy Ross [email protected]

There were two spots where CONFIG_TIMEOUT_64BIT wasn't being correctly
honored, leading to the possibility of long timeouts overflowing
internally and doing weird stuff.

Fixes zephyrproject-rtos#26248

Signed-off-by: Andy Ross <[email protected]>
@zephyrbot zephyrbot added the area: API Changes to public APIs label Jun 17, 2020
@carlescufi carlescufi requested a review from pabigot June 17, 2020 16:09
@jhedberg
Copy link
Member

Seems like we might want to backport this to 2.3.1?

@andyross
Copy link
Contributor Author

Good point. Yes, this is a pure bug fix against 2.3, should be backported. I forget the process :)

@carlescufi carlescufi merged commit 150e18d into zephyrproject-rtos:master Jun 18, 2020
@carlescufi
Copy link
Member

@andyross will you send a PR against the 2.3 branch please?

@andyross
Copy link
Contributor Author

OK, but wasn't there some kind of automated thing that would collect and cherry pick backports?

@jhedberg
Copy link
Member

OK, but wasn't there some kind of automated thing that would collect and cherry pick backports?

@andyross there was, but it hasn't been working for several releases, unfortunately

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: API Changes to public APIs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

A timer with 24-hour timeout fires immediately

6 participants