From: David Miller <davem@davemloft.net>
To: rdunlap@infradead.org
Cc: dledford@redhat.com, saeedm@mellanox.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, leonro@mellanox.com,
jgg@mellanox.com, aviadye@mellanox.com, matanb@mellanox.com,
borisp@mellanox.com
Subject: Re: [pull request][for-next 00/11] Mellanox, mlx5 IPSec updates 2018-02-28-2 (Part 2)
Date: Thu, 08 Mar 2018 14:43:12 -0500 (EST) [thread overview]
Message-ID: <20180308.144312.1291828068384316449.davem@davemloft.net> (raw)
In-Reply-To: <f24845dc-066b-fe78-034f-607aabcc9b67@infradead.org>
From: Randy Dunlap <rdunlap@infradead.org>
Date: Thu, 8 Mar 2018 11:38:02 -0800
> I got this build error in today's linux-next (20180308):
>
> ../drivers/net/ethernet/mellanox/mlx5/core/fs_core.c: In function 'mlx5_init_fs':
> ../drivers/net/ethernet/mellanox/mlx5/core/fs_core.c:2652:2: error: implicit declaration of function 'mlx5_accel_ipsec_device_caps' [-Werror=implicit-function-declaration]
> if (mlx5_accel_ipsec_device_caps(steering->dev) &
> ^
> ../drivers/net/ethernet/mellanox/mlx5/core/fs_core.c:2653:6: error: 'MLX5_ACCEL_IPSEC_DEVICE' undeclared (first use in this function)
> MLX5_ACCEL_IPSEC_DEVICE) {
> ^
> ../drivers/net/ethernet
>
>
> Is this perhaps fixed already?
The very first patch in this series is a fix for this problem.
next prev parent reply other threads:[~2018-03-08 19:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 1:26 [pull request][for-next 00/11] Mellanox, mlx5 IPSec updates 2018-02-28-2 (Part 2) Saeed Mahameed
2018-03-08 1:26 ` [for-next 01/11] net/mlx5: Use MLX5_IPSEC_DEV macro for ipsec caps Saeed Mahameed
2018-03-08 1:26 ` [for-next 02/11] net/mlx5: IPSec, Generalize sandbox QP commands Saeed Mahameed
2018-03-08 1:26 ` [for-next 03/11] net/mlx5e: IPSec, Add support for ESP trailer removal by hardware Saeed Mahameed
2018-03-08 1:26 ` [for-next 04/11] net/mlx5: IPSec, Add command V2 support Saeed Mahameed
2018-03-08 1:26 ` [for-next 05/11] net/mlx5: Export ipsec capabilities Saeed Mahameed
2018-03-08 1:26 ` [for-next 06/11] net/mlx5: Added required metadata capability for ipsec Saeed Mahameed
2018-03-08 1:26 ` [for-next 07/11] net/mlx5: Refactor accel IPSec code Saeed Mahameed
2018-03-08 1:26 ` [for-next 08/11] net/mlx5: Add flow-steering commands for FPGA IPSec implementation Saeed Mahameed
2018-03-08 1:26 ` [for-next 09/11] net/mlx5e: Added common function for to_ipsec_sa_entry Saeed Mahameed
2018-03-08 1:26 ` [for-next 10/11] net/mlx5: IPSec, Add support for ESN Saeed Mahameed
2018-03-08 1:26 ` [for-next 11/11] net/mlx5: Fix wrongly assigned CQ reference counter Saeed Mahameed
2018-03-08 18:04 ` [pull request][for-next 00/11] Mellanox, mlx5 IPSec updates 2018-02-28-2 (Part 2) David Miller
2018-03-08 19:14 ` Doug Ledford
2018-03-08 19:38 ` Randy Dunlap
2018-03-08 19:42 ` Doug Ledford
2018-03-08 19:43 ` David Miller [this message]
2018-03-12 21:43 ` Saeed Mahameed
2018-03-13 1:43 ` Doug Ledford
2018-03-13 19:52 ` Doug Ledford
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=20180308.144312.1291828068384316449.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=saeedm@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;
as well as URLs for NNTP newsgroup(s).