Re: tpmr manpage add veb reference

On Tue, Jul 27, 2021 at 10:18:10PM +0200, Sebastian Benoit wrote: > tpmr(4) connects only two ethernet ports with not much functionality, so the > manpage is helpful by telling us bridge(4) as a more complete alternative. > We now also have veb(4), so mention that as well. > > ok? > > diff --git

Re: sleep.3: miscellaneous cleanup and rewrites

On Mon, Jul 26, 2021 at 10:37:03AM -0600, Todd C. Miller wrote: > On Mon, 26 Jul 2021 07:55:00 -0500, Scott Cheloha wrote: > > > [...] > > > > Anyway, updated patch. No mention of SIGALRM or alarm(3) except in > > the History section. > > I think this is OK for now. > > > Still wondering

tpmr manpage add veb reference

tpmr(4) connects only two ethernet ports with not much functionality, so the manpage is helpful by telling us bridge(4) as a more complete alternative. We now also have veb(4), so mention that as well. ok? diff --git share/man/man4/tpmr.4 share/man/man4/tpmr.4 index ab9eba4cee3..de0b200d429

snmpd: allow sending traps with SNMPv3

This diff allows sending traps in SNMPv3 messages. It defaults to the global seclevel, but it can be specified on a per rule basis. Diff requires both previous setting engineid and ober_dup diff. Tested with netsnmp's snmptrapd and my WIP diff. The other 2 outstanding diffs are for receiving

Re: snmpd(8): Allow setting engineid

Previous diff failed to set the initial bit when not defining engineid in the config. On Fri, 2021-07-23 at 15:41 +0200, Martijn van Duren wrote: > This diff introduces setting the engineid for snmpd(8). > Although this diff might seem quite excessive at first glance, there's > a valid reason to

Re: [please test] amd64: schedule clock interrupts against system clock

On Thu, Jun 24, 2021 at 09:50:07PM -0500, Scott Cheloha wrote: > Hi, > > I'm looking for testers for the attached patch. You need an amd64 > machine with a lapic. > > This includes: > > - All "real" amd64 machines ever made > - amd64 VMs running on hypervisors that provide a virtual lapic > >

Re: pipex(4): introduce mutexes to protect 'pipex_session' context

On Tue, Jul 27, 2021 at 02:44:51AM +0200, Alexander Bluhm wrote: > On Tue, Jul 27, 2021 at 12:30:06AM +0300, Vitaliy Makkoveev wrote: > > > The diff below makes pipex(4) a little bit more parallelization > > > reliable. > > > > @@ -2238,10 +2240,6 @@ pipex_mppe_input(struct mbuf *m0, struct > > >

Don't use named clock in rkpwm

Hi Current rkpwm is assuming "pwm" clock and therefore requires "clock-names" entry in dtb. This has been removed in https://github.com/torvalds/linux/commit/ba0d527be and therefore rkpwm fails with: rkpwm0 at mainbus0: no clock rkpwm1 at mainbus0: no clock which in turn makes the brightness