I did a few patches in January, but also spent plenty of time to raise awareness for the year-2038-Problem, which is more significant than many people assume.

https://www.reddit.com/r/linux/comments/1qfw17a/today_is_y2k38_commemoration_day_t12/ has some info on it.

Older people remember Y2K and think "it was no big deal", but that is because massive effort went into mitigation. And computers back then were big and expensive, while today every smartphone, smart-TV and home-router is a computer with a clock. Even cars.
I already found dozens of issues on x86_64 - so I expect it to be even worse for embedded 32-bit systems.

And if you wonder, how all that relates to reproducible builds... that is where I stumbled over these issues, because we want to ensure that we still get identical binaries later, I set KVM's clock forward by 15 years, because some software will be used for this long and at some point tests started to fail when the clock was past 2038-01-19.