From: patchwork-bot+netdevbpf@kernel.org
To: Arnd Bergmann <arnd@kernel.org>
Cc: saeedm@nvidia.com, leon@kernel.org, davem@davemloft.net,
kuba@kernel.org, tariqt@mellanox.com, maximmi@mellanox.com,
arnd@arndb.de, borisp@nvidia.com, efremov@linux.com,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/mlx5e: fix non-IPV6 build
Date: Fri, 04 Dec 2020 01:20:15 +0000 [thread overview]
Message-ID: <160704481592.10454.9610234423431543181.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201203231314.1483198-1-arnd@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Fri, 4 Dec 2020 00:12:59 +0100 you wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> When IPv6 is disabled, the flow steering code causes a build failure:
>
> drivers/net/ethernet/mellanox/mlx5/core/en_accel/fs_tcp.c:55:14: error: no member named 'skc_v6_daddr' in 'struct sock_common'; did you mean 'skc_daddr'?
> &sk->sk_v6_daddr, 16);
> ^
> include/net/sock.h:380:34: note: expanded from macro 'sk_v6_daddr'
> #define sk_v6_daddr __sk_common.skc_v6_daddr
>
> [...]
Here is the summary with links:
- net/mlx5e: fix non-IPV6 build
https://git.kernel.org/netdev/net-next/c/8a78a440108e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2020-12-04 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 23:12 [PATCH] net/mlx5e: fix non-IPV6 build Arnd Bergmann
2020-12-03 23:17 ` Randy Dunlap
2020-12-04 1:20 ` patchwork-bot+netdevbpf [this message]
2020-12-04 1:47 ` Jakub Kicinski
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=160704481592.10454.9610234423431543181.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=efremov@linux.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maximmi@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@mellanox.com \
/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