netdev - Re: [PATCH net-next 00/11] wireguard updates for 6.19

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251201203713.58118d7e@kernel.org>
Date: Mon, 1 Dec 2025 20:37:13 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: "Jason A. Donenfeld" <Jason@...c4.com>
Cc: netdev@...r.kernel.org, pabeni@...hat.com
Subject: Re: [PATCH net-next 00/11] wireguard updates for 6.19

On Tue, 2 Dec 2025 04:19:27 +0100 Jason A. Donenfeld wrote:
> On Mon, Dec 01, 2025 at 03:07:29PM -0800, Jakub Kicinski wrote:
> > On Mon,  1 Dec 2025 03:28:38 +0100 Jason A. Donenfeld wrote:  
> > > Please find here Asbjørn's yml series. This has been sitting in my
> > > testing for the last week or so, since he sent out the latest series,
> > > and I haven't found any issues so far. Please pull!  
> > 
> > Hi Jason! Thanks for the quick turn around! You say "please pull"
> > did you mean to include a PR in this or should I apply the patches 
> > from the list?  
> 
> I meant from the list, because this is what Dave preferred way back
> when, when WireGuard was a young pup. I actually prefer sending pulls,
> as it feels less redundant and generally unifies my flow with how I
> submit my other trees to Linus, and plus it means you can check a signed
> tag. So I'll make a pull here, below. That gives me the opportunity to
> drop the buggy 10/11 patch too.

FWIW we do still ask for patches to be posted to the list. But some
folks like to do _both_ that and include a branch/signed tag in the
cover letter to pull.

Pulled now, thanks!