linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Saeed Mahameed <saeedm@nvidia.com>,
	Boris Pismenny <borisp@nvidia.com>,
	Leon Romanovsky <leonro@nvidia.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 22 (mlx5)
Date: Thu, 22 Oct 2020 07:52:42 -0700	[thread overview]
Message-ID: <646c66a0-f473-bbe6-960b-42736fcb0006@infradead.org> (raw)
In-Reply-To: <20201022144126.67d0cad9@canb.auug.org.au>

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>

      reply	other threads:[~2020-10-22 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22  3:41 linux-next: Tree for Oct 22 Stephen Rothwell
2020-10-22 14:52 ` Randy Dunlap [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=646c66a0-f473-bbe6-960b-42736fcb0006@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=borisp@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).