* Re: linux-next: Tree for Oct 22 (mlx5)
[not found] <20201022144126.67d0cad9@canb.auug.org.au>
@ 2020-10-22 14:52 ` Randy Dunlap
0 siblings, 0 replies; only message in thread
From: Randy Dunlap @ 2020-10-22 14:52 UTC (permalink / raw)
To: Stephen Rothwell, Linux Next Mailing List
Cc: Linux Kernel Mailing List, netdev, Saeed Mahameed,
Boris Pismenny, Leon Romanovsky, linux-rdma
On 10/21/20 8:41 PM, Stephen Rothwell wrote:
> Hi all,
>
> Since the merge window is open, please do not add any v5.11 material to
> your linux-next included branches until after v5.10-rc1 has been released.
>
> Changes since 20201021:
>
on x86_64:
when CONFIG_IPV6 is not set/enabled:
In file included from ../include/linux/tcp.h:19:0,
from ../include/linux/ipv6.h:88,
from ../include/net/ipv6.h:12,
from ../include/rdma/ib_verbs.h:24,
from ../include/linux/mlx5/device.h:37,
from ../include/linux/mlx5/driver.h:52,
from ../drivers/net/ethernet/mellanox/mlx5/core/en.h:40,
from ../drivers/net/ethernet/mellanox/mlx5/core/en_accel/fs_tcp.h:7,
from ../drivers/net/ethernet/mellanox/mlx5/core/en_accel/fs_tcp.c:5:
../drivers/net/ethernet/mellanox/mlx5/core/en_accel/fs_tcp.c: In function ‘accel_fs_tcp_set_ipv6_flow’:
../include/net/sock.h:380:34: error: ‘struct sock_common’ has no member named ‘skc_v6_daddr’; did you mean ‘skc_daddr’?
#define sk_v6_daddr __sk_common.skc_v6_daddr
^
../drivers/net/ethernet/mellanox/mlx5/core/en_accel/fs_tcp.c:55:14: note: in expansion of macro ‘sk_v6_daddr’
&sk->sk_v6_daddr, 16);
At top level:
../drivers/net/ethernet/mellanox/mlx5/core/en_accel/fs_tcp.c:47:13: warning: ‘accel_fs_tcp_set_ipv6_flow’ defined but not used [-Wunused-function]
static void accel_fs_tcp_set_ipv6_flow(struct mlx5_flow_spec *spec, struct sock *sk)
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
^ permalink raw reply [flat|nested] only message in thread