On 2017/06/08 19:17, Stuart Henderson wrote: > On 2017/06/08 13:54, Ted Unangst wrote: > > Klemens Nanni wrote: > > > This fixes the primitive parsing route of settimeslot() to allow any > > > possible list of slots and/or ranges, see the update manual section. > > > > There doesn't appear to be any use of timeslot code, is there? > > > > Better to delete it entirely. > > ok. > > nsh (in ports) will need changes for the kernel counterpart to this. > Probably nothing else but I'll check.
SIOC[SG]IFTIMESLOT shows up about 17 times in the vendored crap in a load of go ports as usual, but nothing besides nsh that actually uses it.
