Re: Fix and includes on powerpc*

On Sun, May 30, 2021 at 05:03:47AM +, Visa Hankala wrote: > powerpc and powerpc64's include too late > and accidentally rely on other code to pull in the header. If the mutex > header is removed from the , the build fails: > > In file included from src/sys/dev/rnd.c:84: > In file included

Re: Add missing includes

On Sun, May 30, 2021 at 05:01:05AM +, Visa Hankala wrote: > The kernel has places where mutexes are used but is not > included directly. Some of them get exposed when #include > is removed from soft interrupt headers. The following diff fixes them. > > OK? ok jsg@ > > Index:

Fix and includes on powerpc*

powerpc and powerpc64's include too late and accidentally rely on other code to pull in the header. If the mutex header is removed from the , the build fails: In file included from src/sys/dev/rnd.c:84: In file included from src/sys/uvm/uvm_extern.h:180: In file included from

Add missing includes

The kernel has places where mutexes are used but is not included directly. Some of them get exposed when #include is removed from soft interrupt headers. The following diff fixes them. OK? Index: arch/amd64/amd64/db_interface.c

puc(4): [WIP] TXIC TX382B UART controller support (2)

Hi, For long long time, I detached TX382B based UART board and recently I reinstalled it. John Kelly's report "TXIC TX382B UART controller support" (https://marc.info/?l=openbsd-tech=147352668517825) says this controller sometimes lacks THRE interrupt, I found the symptom. I did self loopback

Re: vmd(8): add MTU feature support to vionet device

Mike Larkin writes: > On Mon, May 24, 2021 at 08:25:04AM +0200, Claudio Jeker wrote: >> On Sun, May 23, 2021 at 10:25:38PM -0400, Dave Voutila wrote: >> > The following diff adds in virtio 1.1's VIRTIO_NET_F_MTU feature support >> > to vmd(8)'s virtio networking device. This allows for

Re: systat(1) sticky help

On Tue, Mar 09, 2021 at 07:33:29PM +0100, Martijn van Duren wrote: > I send out an earlier version of this diff to Anindya with some positive > feedback. Instead of claiming another binding, why not make help, order > and view a toggle? I see no reason why this information should disappear > on

Re: [PATCH signify] Add print fingerprint via -F feature

Why does anyone require this functionality? (minus the irony the additional feature is coming from a "slimmed" clone) Paul Spooren wrote: > To know the fingerprint used for a sec/pub/sig the option `-F` is added > which works in combination with `-s`, `-p` or `-x`. It will load the > file and

[PATCH signify] Add print fingerprint via -F feature

To know the fingerprint used for a sec/pub/sig the option `-F` is added which works in combination with `-s`, `-p` or `-x`. It will load the file and and print the used fingerprint in hex. This feature was ported over from OpenWrt's usign[0], which is a slimmed simpler implementation of