netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: netdev@vger.kernel.org
Subject: Re: [pull request][net-next V2 00/15] Mellanox, mlx5 updates 2019-04-02
Date: Mon, 08 Apr 2019 14:32:45 -0700 (PDT)	[thread overview]
Message-ID: <20190408.143245.1691668256420916890.davem@davemloft.net> (raw)
In-Reply-To: <20190405211719.14979-1-saeedm@mellanox.com>

From: Saeed Mahameed <saeedm@mellanox.com>
Date: Fri,  5 Apr 2019 14:17:04 -0700

> This series adds misc updates to mlx5 driver.
> 
> For more information please see tag log below.
> 
> Please pull and let me know if there is any problem.
> 
> v1->v2:
>   remove inline keywords from static functions in c files.

Pulled, thanks Saeed.

The parse_tc_fdb_actions function could use some reverse christmas
tree fixing, just FYI.

> Please note that the series starts with a merge of mlx5-next branch,
> to resolve and avoid dependency with rdma tree.
> 
> Note: when merged with net there is going to be a small merge conflict
> in en_tc.c:
> ++<<<<<<< HEAD
>  +              err = alloc_tc_pedit_action(priv, MLX5_FLOW_NAMESPACE_KERNEL,
>  +                                          parse_attr, hdrs, &action, extack);
> ++=======
> +               err = alloc_tc_pedit_action(priv, MLX5_FLOW_NAMESPACE_FDB,
> +                                           parse_attr, hdrs, extack);
> ++>>>>>>> dave/master
> 
> Resolution:
> +               err = alloc_tc_pedit_action(priv, MLX5_FLOW_NAMESPACE_FDB,
> +                                           parse_attr, hdrs, &action, extack);

Thanks for this, it helped a lot.

      parent reply	other threads:[~2019-04-08 21:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05 21:17 [pull request][net-next V2 00/15] Mellanox, mlx5 updates 2019-04-02 Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 01/15] net/mlx5: Handle event of power detection in the PCIE slot Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 02/15] net/mlx5: E-Switch, Fix double mutex initialization Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 03/15] net/mlx5e: Make the log friendly when decapsulation offload not supported Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 04/15] net/mlx5e: Remove 'parse_attr' argument in parse_tc_fdb_actions() Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 05/15] net/mlx5e: Deletes unnecessary setting of esw_attr->parse_attr Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 06/15] net/mlx5e: Return -EOPNOTSUPP when attempting to offload an unsupported action Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 07/15] net/mlx5e: Use helpers to get headers criteria and value pointers Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 08/15] net/mlx5e: Deny VLAN rewrite if there is no VLAN header match Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 09/15] net/mlx5e: Allow VLAN rewrite of prio field with the same match Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 10/15] net/mlx5e: Offload TC e-switch rules with egress VLAN device Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 11/15] net/mlx5e: Offload TC e-switch rules with ingress " Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 12/15] net/mlx5e: Do not rewrite fields with the same match Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 13/15] net/mlx5: A write memory barrier is sufficient in EQ ci update Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 14/15] net/mlx5e: Obsolete param field holding a constant value Saeed Mahameed
2019-04-05 21:17 ` [net-next V2 15/15] net/mlx5e: Unify logic of MTU boundaries Saeed Mahameed
2019-04-08 21:32 ` David Miller [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=20190408.143245.1691668256420916890.davem@davemloft.net \
    --to=davem@davemloft.net \
    --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).