thanks, committed.
On 2022/03/17 19:16, Martin Vahlensieck wrote:
> Index: if_wg.c
> ===================================================================
> RCS file: /home/reposync/cvs/src/sys/net/if_wg.c,v
> retrieving revision 1.22
> diff -u -p -r1.22 if_wg.c
> --- if_wg.c 22 Feb 2022 01:15:02 -0000 1.22
> +++ if_wg.c 15 Mar 2022 21:10:37 -0000
> @@ -2023,7 +2023,7 @@ wg_input(void *_sc, struct mbuf *m, stru
>
> /*
> * Ensure mbuf is contiguous over full length of packet. This is done
> - * os we can directly read the handshake values in wg_handshake, and so
> + * so we can directly read the handshake values in wg_handshake, and so
> * we can decrypt a transport packet by passing a single buffer to
> * noise_remote_decrypt in wg_decap.
> */
> Index: pf.c
> ===================================================================
> RCS file: /home/reposync/cvs/src/sys/net/pf.c,v
> retrieving revision 1.1125
> diff -u -p -r1.1125 pf.c
> --- pf.c 5 Mar 2022 10:43:32 -0000 1.1125
> +++ pf.c 10 Mar 2022 15:53:51 -0000
> @@ -1340,7 +1340,7 @@ pf_state_expires(const struct pf_state *
> * this function may be called by the state purge task while
> * the state is being modified. avoid inconsistent reads of
> * state->timeout by having the caller do the read (and any
> - * chacks it needs to do on the same variable) and then pass
> + * checks it needs to do on the same variable) and then pass
> * their view of the timeout in here for this function to use.
> * the only consequence of using a stale timeout value is
> * that the state won't be a candidate for purging until the
>
