On Mon, Dec 4, 2017 at 6:30 AM, Arnd Bergmann <arnd@xxxxxxxx> wrote: > On Mon, Dec 4, 2017 at 1:55 AM, Deepa Dinamani <deepa.kernel@xxxxxxxxx> wrote: >> The series is aimed at making input events y2038 safe. >> It extends the lifetime of the realtime timestamps in the >> events to year 2106. >> The series is also a necessary update as glibc is set to provide >> 64 bit time_t support for 32 bit binaries. glibc plan is detailed >> at https://sourceware.org/glibc/wiki/Y2038ProofnessDesign . >> >> The series is a result of discussions with Arnd Bergmann and >> Dmitry Torokhov at last Plumbers. >> >> The plan is to deprecate realtime timestamps anyway as they >> are not appropriate for these timestamps as noted in the patch >> a80b83b7b8 by John Stultz. >> >> The design also updates the format of the input events read/ written >> to the device nodes. This breaks 32 bit interface to the input >> events at compile time as preferred by the maintainer. >> >> The userspace library changes to libevdev, libuinput and mtdev >> will be posted to the respective mailing groups for review. > > Thanks a lot for following up on this! > > Just to clarify, the four patches are all independent of one another > and can be applied in any order, right? I had some comments > for some patches, and I don't want to hold up the other ones > from getting merged this time. There is some minor dependency between patches [2/4] and [3/4]. Patch [3/4] might not apply cleanly without patch [2/4]. But, others are independent. -Deepa -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
