Subject: [PATCH net] drivers: net: ixgbe: Fix *_ipsec_offload_ok():, Use ip_hdr family

: Christian Langrock ---  drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c | 2 +-  drivers/net/ethernet/intel/ixgbevf/ipsec.c | 2 +-  2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c b/drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c index

Subject: [PATCH net] drivers: net: mlx5: Fix *_ipsec_offload_ok(): Use, ip_hdr family

: Christian Langrock ---  drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.c | 2 +-  1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.c b/drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.c index 3d45341e2216..0bab1ceb745c 100644

[RESEND: PATCH net] drivers: net: ixgbe: Fix *_ipsec_offload_ok():, Use ip_hdr family

handling for offloading inter family packets. Signed-off-by: Christian Langrock ---  drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c | 2 +-  drivers/net/ethernet/intel/ixgbevf/ipsec.c | 2 +-  2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/ethernet/intel/ixgbe

[PATCH net] drivers: net: Fix *_ipsec_offload_ok(): Use ip_hdr family

: Christian Langrock ---  drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c   | 2 +-  drivers/net/ethernet/intel/ixgbevf/ipsec.c   | 2 +-  drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec.c | 2 +-  3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/net/ethernet

Re: [PATCH net] drivers: net: Fix *_ipsec_offload_ok(): Use ip_hdr family

Hello David, I saw the status of my patched has been changed to "Changes requested". Can you tell me what can I do to get the patch accepted? Thank you in advance! BR, Christian Am 17.09.20 um 14:27 schrieb Christian Langrock: > Xfrm_dev_offload_ok() is called with the unencrypt

[PATCH] ip/link_vti6.c: Fix local/remote any handling

According to the IPv4 behavior of 'ip' it should be possible to omit the arguments for local and remote address. Without this patch omitting these parameters would lead to uninitialized memory being interpreted as IPv6 addresses. Signed-off-by: Christian Langrock --- ip/link_v

[PATCH] ip/link_vti*.c: Fix output for ikey/okey

ikey and okey are normal u32 values. There's no reason to print them as IPv4/IPv6 addresses. Signed-off-by: Christian Langrock --- ip/link_vti.c | 10 -- ip/link_vti6.c | 10 -- 2 files changed, 8 insertions(+), 12 deletions(-) diff --git a/ip/link_vti.c b/ip/link_vti.c

Re: [PATCH] ip/link_vti*.c: Fix output for ikey/okey

Using hex values sounds reasonable. BR, Christian Updated Patch: Subject: [PATCH] ip/link_vti*.c: Fix output for ikey/okey ikey and okey are normal u32 values. There's no reason to print them as IPv4/IPv6 addresses. Instead print them as hex values. Signed-off-by: Christian Lan

Re: [PATCH] ip/link_vti6.c: Fix local/remote any handling

This seems to be the better solution, at least because i missed the case where the function is called to alter a VTI. BR, Christian Am 07.08.2017 um 17:12 schrieb Stephen Hemminger: > On Mon, 7 Aug 2017 08:41:23 +0200 > Christian Langrock wrote: > >> According to the IPv4 beha