cbb(4): timeout_add(9) -> timeout_add_msec(9), tsleep(9) -> tsleep_nsec(9)

2020-03-05 Thread Scott Cheloha
For the sleep, ticks to milliseconds. The timeout is hz / 10, so 100 milliseconds. While here, also add relevant includes. ok? Index: pci/pccbb.c === RCS file: /cvs/src/sys/dev/pci/pccbb.c,v retrieving revision 1.99 diff -u -p

Re: cz(4): timeout_add(9) -> timeout_add_msec(9), tsleep(9) -> tsleep_nsec(9)

2020-03-05 Thread Scott Cheloha
On Fri, Jan 10, 2020 at 05:41:23PM -0600, Scott Cheloha wrote: > cz(4) is apparently not compiled, but it keeps showing up in my symbol > searches, so I'll just convert it to reduce noise. > > Here the code is converting CZ_POLL_MS to ticks. We can just use that > constant directly with

regress: bgpd: config: Fix attribute ordering

2020-03-05 Thread Klemens Nanni
I ran bgpd to test diffs and stumbled across what looks like simple disorder in the config checks. bgpd must have changed in how it orders attributes within `set { ... }' blocks; breaking the sets into multiple lines and diffing line-wise instead of word-wise shows that the printed config

Re: lcd(4/hppa): timeout_add(9) -> timeout_add_usec(9)

2020-03-05 Thread Mark Kettenis
> Date: Sat, 8 Feb 2020 13:15:47 -0600 > From: Scott Cheloha > > On Sun, Dec 22, 2019 at 01:17:56PM -0600, Scott Cheloha wrote: > > lcd_softc.sc_delay's unit appears to be microseconds. > > > > ok? > > 1 month bump. Finaly verified that it works. ok kettenis@ > Index: dev/lcd.c >

Re: Compiler warning in ctype.h

2020-03-05 Thread Theo de Raadt
Todd C. Miller wrote: > On Thu, 05 Mar 2020 16:07:48 +0100, Thomas de Grivel wrote: > > > Actually I see the same problem on 6.6-stable : > > including readline/readline.h produces warnings. > > > > Any -Werror hope some day ? > > You still haven't bothered to include: > > 1) the compiler you

Re: Compiler warning in ctype.h

2020-03-05 Thread Todd C . Miller
On Thu, 05 Mar 2020 16:07:48 +0100, Thomas de Grivel wrote: > Actually I see the same problem on 6.6-stable : > including readline/readline.h produces warnings. > > Any -Werror hope some day ? You still haven't bothered to include: 1) the compiler you are using 2) the compiler flags to

Re: Compiler warning in ctype.h

2020-03-05 Thread Thomas de Grivel
Actually I see the same problem on 6.6-stable : including readline/readline.h produces warnings. Any -Werror hope some day ? cheers Le mer. 4 mars 2020 à 13:41, Thomas de Grivel a écrit : > > With latest OpenBSD snapshot on amd64 > > In file included from /usr/include/readline/chardefs.h:26, >

fcntl unlock

2020-03-05 Thread Anton Lindqvist
Hi, After reading the fcntl(2) code I cannot spot anything obvious preventing it from being unlocked[1]. This is all made possible by the recent MP-safe effort including resource limits, atomic file flags, ioctl unlock and posix file locks. I've been running with this for a week by now. However,