[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171011064446.GA2039@nanopsycho>
Date: Wed, 11 Oct 2017 08:44:46 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Or Gerlitz <gerlitz.or@...il.com>
Cc: Saeed Mahameed <saeedm@...lanox.com>,
Linux Netdev List <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Jamal Hadi Salim <jhs@...atatu.com>,
Cong Wang <xiyou.wangcong@...il.com>,
mlxsw <mlxsw@...lanox.com>
Subject: Re: [patch net-next 0/4] net: sched: get rid of
cls_flower->egress_dev
Tue, Oct 10, 2017 at 11:46:22PM CEST, gerlitz.or@...il.com wrote:
>On Wed, Oct 11, 2017 at 12:13 AM, Jiri Pirko <jiri@...nulli.us> wrote:
>> Tue, Oct 10, 2017 at 07:24:21PM CEST, gerlitz.or@...il.com wrote:
>
>> Or, as I replied to you earlier, the issue you describe is totally
>> unrelated to this patchset as you see the issue with the current net-next.
>
>Jiri, the point I wanted to make that if indeed there's a bug in mlx5
>or flower, we will have to fix it for 4.14 and then these bits would
>have to be rebased when net-next is re-planted over net, I put "FWIW"
>before that, so maybe it doesn't W so much, we'll see.
The fix is still unrelated to this patchset.
Powered by blists - more mailing lists