netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeedm@mellanox.com>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leonro@mellanox.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	Boris Pismenny <borisp@mellanox.com>,
	"Aviad Yehezkel" <aviadye@mellanox.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"dledford@redhat.com" <dledford@redhat.com>,
	Matan Barak <matanb@mellanox.com>
Subject: Re: [for-next 10/14] net/mlx5: Add shim layer between fs and cmd
Date: Wed, 7 Mar 2018 05:54:17 +0000	[thread overview]
Message-ID: <1520402055.24565.29.camel@mellanox.com> (raw)
In-Reply-To: <20180305210310.GV11337@mellanox.com>

On Mon, 2018-03-05 at 14:03 -0700, Jason Gunthorpe wrote:
> On Mon, Mar 05, 2018 at 12:46:33PM -0800, Saeed Mahameed wrote:
> 
> > +static struct mlx5_flow_cmds mlx5_flow_cmds = {
> 
> 'static const' on these new static structs?
> 

Yes, Will fix.

> Jason


  reply	other threads:[~2018-03-07  5:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 20:46 [pull request][for-next 00/14] Mellanox, mlx5 IPSec updates 2018-02-28-1 Saeed Mahameed
2018-03-05 20:46 ` [for-next 01/14] net/mlx5: Fixed sparse issues Saeed Mahameed
2018-03-05 20:53   ` Or Gerlitz
2018-03-07  6:05     ` Saeed Mahameed
2018-03-05 20:55   ` Sergei Shtylyov
2018-03-05 20:46 ` [for-next 02/14] IB/mlx5: Removed not used parameters Saeed Mahameed
2018-03-05 20:54   ` Jason Gunthorpe
2018-03-05 20:46 ` [for-next 03/14] net/mlx5: Fixed compilation issue when CONFIG_MLX5_ACCEL is disabled Saeed Mahameed
2018-03-05 20:46 ` [for-next 04/14] net/mlx5e: Wait for FPGA command responses with a timeout Saeed Mahameed
2018-03-05 20:46 ` [for-next 05/14] net/mlx5e: Fixed sleeping inside atomic context Saeed Mahameed
2018-03-05 20:46 ` [for-next 06/14] net/mlx5e: Removed not need synchronize_rcu Saeed Mahameed
2018-03-05 20:46 ` [for-next 07/14] net/mlx5: FPGA and IPSec initialization to be before flow steering Saeed Mahameed
2018-03-05 20:46 ` [for-next 08/14] IB/mlx5: Pass mlx5_flow_act struct instead of multiple arguments Saeed Mahameed
2018-03-05 21:05   ` Jason Gunthorpe
2018-03-05 20:46 ` [for-next 09/14] {net,IB}/mlx5: Add has_tag to mlx5_flow_act Saeed Mahameed
2018-03-05 21:07   ` Jason Gunthorpe
2018-03-07  6:01     ` Saeed Mahameed
2018-03-05 20:46 ` [for-next 10/14] net/mlx5: Add shim layer between fs and cmd Saeed Mahameed
2018-03-05 21:03   ` Jason Gunthorpe
2018-03-07  5:54     ` Saeed Mahameed [this message]
2018-03-05 20:46 ` [for-next 11/14] net/mlx5: Add empty egress namespace to flow steering core Saeed Mahameed
2018-03-05 20:46 ` [for-next 12/14] net/mlx5: Embed mlx5_flow_act into fs_fte Saeed Mahameed
2018-03-05 20:46 ` [for-next 13/14] {net,IB}/mlx5: Add flow steering helpers Saeed Mahameed
2018-03-05 20:46 ` [for-next 14/14] net/mlx5: Flow steering cmd interface should get the fte when deleting 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=1520402055.24565.29.camel@mellanox.com \
    --to=saeedm@mellanox.com \
    --cc=aviadye@mellanox.com \
    --cc=borisp@mellanox.com \
    --cc=davem@davemloft.net \
    --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 \
    /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).