distexpand for autogenerated upstream distfile resources (was: standardize and simplify GitHub submodule handling in ports?)

2023-08-08 Thread Thomas Frohwein
On Mon, Aug 07, 2023 at 09:17:05PM +0100, Stuart Henderson wrote: [...] > I think maybe I'd prefer to have some variable that could be used > *instead* of the existing GH_* variables rather than in conjunction with > them (so they can be used for all GH archive ports, rather than have > them a

Re: sosetopt(): merge SO_SND* with corresponding SO_RCV* cases

2023-08-08 Thread Alexander Bluhm
On Wed, Aug 09, 2023 at 12:41:18AM +0300, Vitaliy Makkoveev wrote: > I think it's better to merge SO_BINDANY cases from both switch blocks. > This time SO_LINGER case is separated, so there is no reason for > dedicated switch block. OK bluhm@ > Index: sys/kern/uipc_socket.c >

Re: sosetopt(): merge SO_SND* with corresponding SO_RCV* cases

2023-08-08 Thread Vitaliy Makkoveev
On Tue, Aug 08, 2023 at 10:40:46PM +0200, Alexander Bluhm wrote: > On Fri, Aug 04, 2023 at 12:38:23AM +0300, Vitaliy Makkoveev wrote: > > @@ -1856,6 +1856,9 @@ sosetopt(struct socket *so, int level, i > > case SO_SNDLOWAT: > > case SO_RCVLOWAT: > > { > > +

Re: sosetopt(): merge SO_SND* with corresponding SO_RCV* cases

2023-08-08 Thread Alexander Bluhm
On Fri, Aug 04, 2023 at 12:38:23AM +0300, Vitaliy Makkoveev wrote: > @@ -1856,6 +1856,9 @@ sosetopt(struct socket *so, int level, i > case SO_SNDLOWAT: > case SO_RCVLOWAT: > { > + struct sockbuf *sb = (optname == SO_SNDBUF || > +

Re: pf(4) may cause relayd(8) to abort

2023-08-08 Thread Alexander Bluhm
On Tue, Aug 01, 2023 at 01:50:52AM +0200, Alexandr Nedvedicky wrote: > OK to commit? OK bluhm@ > 8<---8<---8<--8< > diff --git a/sys/net/pf_table.c b/sys/net/pf_table.c > index 6f23a6f795d..c862c804f84 100644 > --- a/sys/net/pf_table.c >

Re: agtimer(4/arm64): simplify agtimer_delay()

2023-08-08 Thread Mark Kettenis
> From: Dale Rahn > Date: Tue, 8 Aug 2023 12:36:45 -0400 > > Switching the computation of cycles/delaycnt to a proper 64 value math > instead of the '32 bit safe' complex math is likely a good idea. > However I am not completely convinced that switching to 'yield' (current > CPU_BUSY_CYCLE

Re: EVFILT_TIMER add support for different timer precisions NOTE_{,U,N,M}SECONDS

2023-08-08 Thread Claudio Jeker
On Tue, Aug 08, 2023 at 10:40:06AM -0500, Scott Cheloha wrote: > On Sat, Aug 05, 2023 at 01:33:05AM -0400, A Tammy wrote: > > > > On 8/5/23 00:49, Scott Cheloha wrote: > > > On Sat, Aug 05, 2023 at 12:17:48AM -0400, aisha wrote: > > >> On 22/09/10 01:53PM, Visa Hankala wrote: > > >>> On Wed, Aug

Re: agtimer(4/arm64): simplify agtimer_delay()

2023-08-08 Thread Dale Rahn
Switching the computation of cycles/delaycnt to a proper 64 value math instead of the '32 bit safe' complex math is likely a good idea. However I am not completely convinced that switching to 'yield' (current CPU_BUSY_CYCLE implementation) for every loop of a 'short wait' in the wait loop makes

Re: EVFILT_TIMER add support for different timer precisions NOTE_{,U,N,M}SECONDS

2023-08-08 Thread Scott Cheloha
On Sat, Aug 05, 2023 at 01:33:05AM -0400, A Tammy wrote: > > On 8/5/23 00:49, Scott Cheloha wrote: > > On Sat, Aug 05, 2023 at 12:17:48AM -0400, aisha wrote: > >> On 22/09/10 01:53PM, Visa Hankala wrote: > >>> On Wed, Aug 31, 2022 at 04:48:37PM -0400, aisha wrote: > I've added a patch which

Re: PATCH: a bit of introspection in make

2023-08-08 Thread Marc Espie
Actually, as far as bsd.port.mk, it doesn't need to move too much stuff around thanks to make's lazyness. Note that having a list of defined MASTER_SITES variables simplifies the check. I've also added a check for the right MASTER_SITES to be defined, since currently we do not error out until

Re: PATCH: a bit of introspection in make

2023-08-08 Thread Marc Espie
Here's a revised diff (reordered plus actual use of the boolean) plus concrete example use for bsd.port.mk (disregarding the fact _ALL_VARIABLES would have to move *after* all MASTER_SITES have been defined. Index: var.c === RCS