| created | 2021-01-21T21:22:42Z |
|---|---|
| begin | 2021-01-13T12:38:36Z |
| end | 2021-01-13T16:28:50Z |
| path | src/sys |
| commits | 2 |
| date | 2021-01-13T16:28:49Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/arch/mips64/mips64/mips64_machdep.c | log | diff | annotate |
| src/sys/kern/kern_clock.c | log | diff | annotate | |
| message |
kernel, sysctl(8): remove dead variable: tickadj The global "tickadj" variable is a remnant of the old NTP adjustment code we used in the kernel before the current timecounter subsystem was imported from FreeBSD circa 2004 or 2005. Fifteen years hence it is completely vestigial and we can remove it. We probably should have removed it long ago but I guess it slipped through the cracks. FreeBSD removed it in 2002: https://cgit.freebsd.org/src/commit/?id=e1d970f1811e5e1e9c912c032acdcec6521b2a6d NetBSD and DragonflyBSD can probably remove it, too. We export tickadj via the kern.clockrate sysctl(2), so update sysctl.2 and sysctl(8) accordingly. Hypothetically this change could break someone's sysctl(8) parsing script. I don't think that's very likely. ok mvs@ |
|||
| date | 2021-01-13T16:28:50Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/conf/param.c | log | diff | annotate |
| src/sys/sys/kernel.h | log | diff | annotate | |
| src/sys/sys/time.h | log | diff | annotate | |
| message |
kernel, sysctl(8): remove dead variable: tickadj The global "tickadj" variable is a remnant of the old NTP adjustment code we used in the kernel before the current timecounter subsystem was imported from FreeBSD circa 2004 or 2005. Fifteen years hence it is completely vestigial and we can remove it. We probably should have removed it long ago but I guess it slipped through the cracks. FreeBSD removed it in 2002: https://cgit.freebsd.org/src/commit/?id=e1d970f1811e5e1e9c912c032acdcec6521b2a6d NetBSD and DragonflyBSD can probably remove it, too. We export tickadj via the kern.clockrate sysctl(2), so update sysctl.2 and sysctl(8) accordingly. Hypothetically this change could break someone's sysctl(8) parsing script. I don't think that's very likely. ok mvs@ |
|||