On Fri, Feb 10, 2023 at 5:04 PM John Stultz <jstultz@xxxxxxxxxx> wrote: > Thomas' patch fixes the erronious 0-as-invalid initialization issue > using KTIME_MAX but also simplifies the logic getting rid of the > freezer handling. > > I don't have as much familiarity with the freezer handling change, so > while it looks sane, I can't say I would likely catch an issue doing a > visual review. Actually, because of this, I'm going to split Thomas' change in two. The first to just use KTIME_MAX as the invalid initialization value, and the second to cleanup the freezer logic. That way if the freezer change is problematic we can revert it and not lose the fix here. thanks -john
