netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: David Miller <davem@davemloft.net>, saeedm@mellanox.com
Cc: 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 V2 00/13] Mellanox, mlx5 IPSec updates 2018-02-28-1
Date: Wed, 07 Mar 2018 15:57:46 -0500	[thread overview]
Message-ID: <1520456266.3126.56.camel@redhat.com> (raw)
In-Reply-To: <1520455310.3126.53.camel@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2669 bytes --]

On Wed, 2018-03-07 at 15:41 -0500, Doug Ledford wrote:
> On Wed, 2018-03-07 at 15:31 -0500, David Miller wrote:
> > From: Saeed Mahameed <saeedm@mellanox.com>
> > Date: Tue,  6 Mar 2018 22:35:03 -0800
> > 
> > > This series includes shared code updates for mlx5 core driver for both
> > > netdev and rdma subsystems.  This series should be pulled to both
> > > trees so we can continue netdev and rdma specific submissions separately.
> > > 
> > > For more information please see tag log below.
> > > 
> > > The series doesn't cause any conflict with the latest mlx5 rc fixes.
> > > 
> > > v1->v2:
> > >   - Drop sparse fixes patch
> > >   - Updated commit message of "net/mlx5: Add has_tag to mlx5_flow_act"
> > >   - Add const to  static mlx5_flow_cmd structs where needed.
> > 
> > Pulled, thanks Saeed.
> 
> Thanks, pulled here as well.
> 

Just FYI,

My .config might have been in an unreasonable state (I had jumped from
for-next to for-rc, built a kernel which ran a make oldconfig, then
jumped back to for-next and tried to build with this series applied but
without making any changes to the .config file), but I got a build
error.  My .config had both innova and the new ipsec accelerator turned
off or something like that, and I got this error:

  CC [M]  drivers/net/ethernet/mellanox/mlx5/core/en_main.o
drivers/net/ethernet/mellanox/mlx5/core/fs_core.c: In function
‘mlx5_init_fs’:
drivers/net/ethernet/mellanox/mlx5/core/fs_core.c:2645:6: error:
implicit declaration of function ‘mlx5_accel_ipsec_device_caps’; did you
mean ‘mlx5_accel_ipsec_cleanup’? [-Werror=implicit-function-declaration]
  if (mlx5_accel_ipsec_device_caps(steering->dev) &
      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
      mlx5_accel_ipsec_cleanup
  CC [M]  drivers/net/ethernet/silan/sc92031.o
  CC [M]  drivers/w1/slaves/w1_smem.o
  CC [M]  drivers/net/ethernet/mellanox/mlx5/core/en_common.o
  CC [M]  drivers/net/ethernet/sfc/falcon/nic.o
drivers/net/ethernet/mellanox/mlx5/core/fs_core.c:2646:6: error:
‘MLX5_ACCEL_IPSEC_DEVICE’ undeclared (first use in this function); did
you mean ‘__MLX5_ACCEL_IPSEC_H__’?
      MLX5_ACCEL_IPSEC_DEVICE) {
      ^~~~~~~~~~~~~~~~~~~~~~~
      __MLX5_ACCEL_IPSEC_H__
drivers/net/ethernet/mellanox/mlx5/core/fs_core.c:2646:6: note: each
undeclared identifier is reported only once for each function it appears
in
  CC [M]  drivers/w1/w1.o

Running make config and enabling innova support and ipsec accelerator
support fixed it.

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-03-07 20:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07  6:35 [pull request][for-next V2 00/13] Mellanox, mlx5 IPSec updates 2018-02-28-1 Saeed Mahameed
2018-03-07  6:35 ` [for-next V2 01/13] IB/mlx5: Removed not used parameters Saeed Mahameed
2018-03-07  6:35 ` [for-next V2 02/13] net/mlx5: Fixed compilation issue when CONFIG_MLX5_ACCEL is disabled Saeed Mahameed
2018-03-07  6:35 ` [for-next V2 03/13] net/mlx5e: Wait for FPGA command responses with a timeout Saeed Mahameed
2018-03-07 10:25   ` Kirill Tkhai
2018-03-07 20:01     ` Saeed Mahameed
2018-03-07  6:35 ` [for-next V2 04/13] net/mlx5e: Fixed sleeping inside atomic context Saeed Mahameed
2018-03-07  6:35 ` [for-next V2 05/13] net/mlx5e: Removed not need synchronize_rcu Saeed Mahameed
2018-03-07  6:35 ` [for-next V2 06/13] net/mlx5: FPGA and IPSec initialization to be before flow steering Saeed Mahameed
2018-03-07  6:35 ` [for-next V2 07/13] IB/mlx5: Pass mlx5_flow_act struct instead of multiple arguments Saeed Mahameed
2018-03-07  6:35 ` [for-next V2 08/13] {net,IB}/mlx5: Add has_tag to mlx5_flow_act Saeed Mahameed
2018-03-07  6:35 ` [for-next V2 09/13] net/mlx5: Add shim layer between fs and cmd Saeed Mahameed
2018-03-07  6:35 ` [for-next V2 10/13] net/mlx5: Add empty egress namespace to flow steering core Saeed Mahameed
2018-03-07  6:35 ` [for-next V2 11/13] net/mlx5: Embed mlx5_flow_act into fs_fte Saeed Mahameed
2018-03-07  6:35 ` [for-next V2 12/13] {net,IB}/mlx5: Add flow steering helpers Saeed Mahameed
2018-03-07 19:58   ` Doug Ledford
2018-03-07  6:35 ` [for-next V2 13/13] net/mlx5: Flow steering cmd interface should get the fte when deleting Saeed Mahameed
2018-03-07 19:57 ` [pull request][for-next V2 00/13] Mellanox, mlx5 IPSec updates 2018-02-28-1 Doug Ledford
2018-03-07 20:31 ` David Miller
2018-03-07 20:41   ` Doug Ledford
2018-03-07 20:57     ` Doug Ledford [this message]
2018-03-07 23:13       ` Saeed Mahameed

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=1520456266.3126.56.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=aviadye@mellanox.com \
    --cc=borisp@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=jgg@mellanox.com \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=matanb@mellanox.com \
    --cc=netdev@vger.kernel.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).