On Thu, Jun 03, 2021 at 01:09:48AM +0200, Alexandr Nedvedicky wrote:
> > pf_purge_expired_states(u_int32_t maxcheck)
> > {
>
> > - cur = pf_state_ref(next);
> > + do {
> > + if ((cur->timeout == PFTM_UNLINKED) ||
> > + (pf_state_expires(cur) <= getuptime())) {
On Thu, Jun 03, 2021 at 01:09:48AM +0200, Alexandr Nedvedicky wrote:
> Hello,
>
> looks like my earlier mail got eaten by SPAM filter, let's try again...
>
>
> >
> > moving pf locks to mutexes makes sense to me, but like you say,
> > this will need testing and experimentation. one of the issues
I am satisfied.
That is one architecture. I suggest checking which others can use
the same treatment.
Frederic Cambus wrote:
> On Mon, May 31, 2021 at 12:57:47PM +0200, Mark Kettenis wrote:
>
> > > +option FONT_SPLEEN8x16
> > > +option FONT_SPLEEN12x24
> > > +option
Am Wed, Jun 02, 2021 at 10:37:36PM +0200 schrieb Mark Kettenis:
> Linux folks changed the device tree to use 10gbase-r instead of
> 10gbase-kr since "it is more correct". Then the UEFI folks synched
> their device trees to Linux and the 10G ports broke. So accept both
> in the code.
>
> ok?
>
On Mon, May 31, 2021 at 12:57:47PM +0200, Mark Kettenis wrote:
> > +option FONT_SPLEEN8x16
> > +option FONT_SPLEEN12x24
> > +option FONT_SPLEEN16x32
> > +option FONT_SPLEEN32x64
> > +
> > option RAMDISK_HOOKS
> > option MINI
Linux folks changed the device tree to use 10gbase-r instead of
10gbase-kr since "it is more correct". Then the UEFI folks synched
their device trees to Linux and the 10G ports broke. So accept both
in the code.
ok?
Index: dev/fdt/if_mvpp.c
=
Hi,
feeling hesitant to commit into ksh without at least one proper OK,
i'm resending this patch here, sorry if i missed private feedback.
What the existing code does:
It tries to make sure that multi-byte UTF-8 characters get passed on by
the shell without fragmentation, not one byte at time. I
ping
Dave Voutila writes:
> Dave Voutila writes:
>
>> The conclusion of my previous fixes to vmd(8) [1] changes the event
>> handling in vmctl(8) to support receiving IMSG_VMDOP_TERMINATE_VM_EVENTs
>> from the control process. (This removes a XXX comment from vmd.)
>>
>> For clarity, the messag
Claudio Jeker writes:
> On Wed, Jun 02, 2021 at 08:24:53AM -0400, Dave Voutila wrote:
>>
>> Martin Vahlensieck writes:
>>
>> > Index: parse.y
>> > ===
>> > retrieving revision 1.56
>> > diff -u -p -r1.56 parse.y
>> > --- parse.y
On Wed, Jun 02, 2021 at 11:09:13AM +1000, David Gwynne wrote:
> if a bridge checked the ipv4 checksum and it was good, we can avoid
> checking it again in ip_input.
>
> ok?
>
ok mvs@
> Index: ip_input.c
> ===
> RCS file: /cvs/src/s
On Wed, Jun 02, 2021 at 08:24:53AM -0400, Dave Voutila wrote:
>
> Martin Vahlensieck writes:
>
> > Index: parse.y
> > ===
> > retrieving revision 1.56
> > diff -u -p -r1.56 parse.y
> > --- parse.y 23 Sep 2020 19:18:18 - 1.56
Martin Vahlensieck writes:
> Index: parse.y
> ===
> retrieving revision 1.56
> diff -u -p -r1.56 parse.y
> --- parse.y 23 Sep 2020 19:18:18 - 1.56
> +++ parse.y 2 Jun 2021 06:48:12 -
> @@ -694,6 +694,9 @@ lladdr
On Tue, Jun 01, 2021 at 09:29:55AM BST, Patrick Wildt wrote:
> Am Mon, Feb 22, 2021 at 08:10:21PM +0100 schrieb Patrick Wildt:
> > Hi,
> >
> > it seems like some eMMCs are not capable of doing 8-bit operation,
> > even if the controller supports it. I was questioning our drivers
> > first, but it
On Wed, May 19, 2021 at 01:48:26AM +0200, Alexandr Nedvedicky wrote:
> Hello,
>
> just for the record...
>
>
>
> > > in current tree the ether_input() is protected by NET_LOCK(), which is
> > > grabbed
> > > by caller as a writer. bluhm's diff changes NET_LOCK() readlock, so
> > > ether_input(
Hi Dave
On Tue, Jun 01, 2021 at 08:23:45PM -0400, Dave Voutila wrote:
>
> Martin Vahlensieck writes:
>
> > Hi
> >
> > The grammar for lladdr of interfaces is according to the manpage:
> >
> > [locked] lladdr [etheraddr]
> >
> > This implies that `locked lladdr' is OK but looking at parse.y thi
15 matches
Mail list logo
