From: Saeed Mahameed <saeed@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Ariel Levkovich <lariel@mellanox.com>,
Roi Dayan <roid@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Vlad Buslov <vladbu@nvidia.com>
Subject: Re: [net-next 05/15] net/mlx5: Refactor tc flow attributes structure
Date: Wed, 23 Sep 2020 11:24:52 -0700 [thread overview]
Message-ID: <d8c43d2db17ebd24744fe45ae9c4e2005a79fb86.camel@kernel.org> (raw)
In-Reply-To: <20200923101817.0b0a79c3@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Wed, 2020-09-23 at 10:18 -0700, Jakub Kicinski wrote:
> On Tue, 22 Sep 2020 23:24:28 -0700 saeed@kernel.org wrote:
> > Signed-off-by: Ariel Levkovich <lariel@mellanox.com>
> > Reviewed-by: Roi Dayan <roid@mellanox.com>
> > Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
> >
> > fixup! net/mlx5: Refactor tc flow attributes structure
> >
> > Init the parse_attr pointer in the beginning of
> > parse_tc_fdb_actions
> > so it will be valid for the entire method.
> >
> > Signed-off-by: Ariel Levkovich <lariel@mellanox.com>
> > Reviewed-by: Vlad Buslov <vladbu@nvidia.com>
> > Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
>
> fixup
:-/ .. no clue how this happened
will fix, thanks.
next prev parent reply other threads:[~2020-09-23 18:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 6:24 [pull request][net-next 00/15] mlx5 Connection Tracking in NIC mode saeed
2020-09-23 6:24 ` [net-next 01/15] net/mlx5: Refactor multi chains and prios support saeed
2020-09-23 6:24 ` [net-next 02/15] net/mlx5: Allow ft level ignore for nic rx tables saeed
2020-09-23 6:24 ` [net-next 03/15] net/mlx5e: Tc nic flows to use mlx5_chains flow tables saeed
2020-09-23 6:24 ` [net-next 04/15] net/mlx5e: Split nic tc flow allocation and creation saeed
2020-09-23 6:24 ` [net-next 05/15] net/mlx5: Refactor tc flow attributes structure saeed
2020-09-23 17:18 ` Jakub Kicinski
2020-09-23 18:24 ` Saeed Mahameed [this message]
2020-09-23 6:24 ` [net-next 06/15] net/mlx5e: Add tc chains offload support for nic flows saeed
2020-09-23 6:24 ` [net-next 07/15] net/mlx5e: rework ct offload init messages saeed
2020-09-23 6:24 ` [net-next 08/15] net/mlx5e: Support CT offload for tc nic flows saeed
2020-09-23 6:24 ` [net-next 09/15] net/mlx5e: CT: Use the same counter for both directions saeed
2020-09-23 6:24 ` [net-next 10/15] net/mlx5e: TC: Remove unused parameter from mlx5_tc_ct_add_no_trk_match() saeed
2020-09-23 6:24 ` [net-next 11/15] net/mlx5e: Keep direct reference to mlx5_core_dev in tc ct saeed
2020-09-23 6:24 ` [net-next 12/15] net/mlx5e: IPsec: Use kvfree() for memory allocated with kvzalloc() saeed
2020-09-23 6:24 ` [net-next 13/15] net/mlx5e: Use kfree() to free fd->g in accel_fs_tcp_create_groups() saeed
2020-09-23 6:24 ` [net-next 14/15] net/mlx5: simplify the return expression of mlx5_ec_init() saeed
2020-09-23 6:24 ` [net-next 15/15] net/mlx5: remove unreachable return saeed
2020-09-23 17:21 ` [pull request][net-next 00/15] mlx5 Connection Tracking in NIC mode Jakub Kicinski
2020-09-23 18:23 ` 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=d8c43d2db17ebd24744fe45ae9c4e2005a79fb86.camel@kernel.org \
--to=saeed@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=lariel@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=roid@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=vladbu@nvidia.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).