aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/LICENSES/dual
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2022-05-04 17:50:00 -0700
committerJakub Kicinski <kuba@kernel.org>2022-05-04 17:50:00 -0700
commit205557ba9904eec0a8e9ca28ec32e567f5027338 (patch)
treed25c3d9d7ead417a3ecdc7fca002aaead4a1bd4f /LICENSES/dual
parentMerge tag 'mlx5-fixes-2022-05-03' of git://git.kernel.org/pub/scm/linux/kernel/g (diff)
parentwireguard: selftests: set panic_on_warn=1 from cmdline (diff)
downloadwireguard-linux-stable.tar.xz
wireguard-linux-stable.zip
Merge branch 'wireguard-patches-for-5-18-rc6'HEADstable
Jason A. Donenfeld says: ==================== wireguard patches for 5.18-rc6 In working on some other problems, I wound up leaning on the WireGuard CI more than usual and uncovered a few small issues with reliability. These are fairly low key changes, since they don't impact kernel code itself. One change does stick out in particular, though, which is the "make routing loop test non-fatal" commit. I'm not thrilled about doing this, but currently [1] remains unsolved, and I'm still working on a real solution to that (hopefully for 5.19 or 5.20 if I can come up with a good idea...), so for now that test just prints a big red warning instead. [1] https://lore.kernel.org/netdev/YmszSXueTxYOC41G@zx2c4.com/ ==================== Link: https://lore.kernel.org/r/20220504202920.72908-1-Jason@zx2c4.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'LICENSES/dual')
0 files changed, 0 insertions, 0 deletions