From: Saeed Mahameed <saeedm@mellanox.com>
To: "davem@davemloft.net" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Or Gerlitz <ogerlitz@mellanox.com>
Subject: Re: mlx5 stable backport help
Date: Wed, 20 Feb 2019 20:01:00 +0000 [thread overview]
Message-ID: <33b67a2b9a67bc9fe307edc0a3eeeab875598a09.camel@mellanox.com> (raw)
In-Reply-To: <20190219.223612.1535166672416390768.davem@davemloft.net>
On Tue, 2019-02-19 at 22:36 -0800, David Miller wrote:
> Saeed and Or,
>
> I need help backporting two changes for -stable. Namely:
Hi Dave Thanks for trying,
>
> 6707f74be8621ae067d2cf1c4485900e2742c20f ("net/mlx5e: Update hw flows
> when encap source mac changed")
The fixes tag of the above commit is wrong and it should have been
commit e32ee6c78efa6a32bff782bbe7a9970b018996ca
Author: Eli Britstein <elibr@mellanox.com>
Date: Mon Dec 3 17:09:54 2018 +0200
net/mlx5e: Support tunnel encap over tagged Ethernet
Before this patch we didn't have the support for "tunnel encap over
tagged Ethernet" which introduced the whole route_dev logic to generate
the encap headers, so the patch should only exist in -rc, let's just
skip it.
> 218d05ce326f9e1b40a56085431fa1068b43d5d9 ("net/mlx5e: Don't overwrite
> pedit action when multiple pedit used")
>
I tried and this patch applies smoothly on 4.19.
let me know if you need further assistance.
Thanks,
Saeed
> For example, with the first one, not only has the code moved into
> tc_tun.c but also we require the addition of
> get_route_and_out_devs(),
> the passing in of the &route_dev, and also all of the new
> dst_is_lag_dev logic. That's like 4 or 5 commits worth.
>
> Thanks.
next prev parent reply other threads:[~2019-02-20 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 6:36 mlx5 stable backport help David Miller
2019-02-20 20:01 ` Saeed Mahameed [this message]
2019-02-20 20:27 ` David Miller
2019-02-20 23:58 ` Saeed Mahameed
2019-02-21 0:21 ` David Miller
2019-02-21 0:43 ` Saeed Mahameed
2019-02-21 10:21 ` Or Gerlitz
2019-02-21 22:35 ` Saeed Mahameed
2019-02-22 9:13 ` Or Gerlitz
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=33b67a2b9a67bc9fe307edc0a3eeeab875598a09.camel@mellanox.com \
--to=saeedm@mellanox.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@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