From: Jiri Pirko <jiri@resnulli.us>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: Saeed Mahameed <saeedm@mellanox.com>,
Linux Netdev List <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>, mlxsw <mlxsw@mellanox.com>
Subject: Re: [patch net-next 0/4] net: sched: get rid of cls_flower->egress_dev
Date: Wed, 11 Oct 2017 08:44:46 +0200 [thread overview]
Message-ID: <20171011064446.GA2039@nanopsycho> (raw)
In-Reply-To: <CAJ3xEMizUNPzPAjWuk-PpkK88UgD9OmOGORiEO64r0dx-GfcBw@mail.gmail.com>
Tue, Oct 10, 2017 at 11:46:22PM CEST, gerlitz.or@gmail.com wrote:
>On Wed, Oct 11, 2017 at 12:13 AM, Jiri Pirko <jiri@resnulli.us> wrote:
>> Tue, Oct 10, 2017 at 07:24:21PM CEST, gerlitz.or@gmail.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.
prev parent reply other threads:[~2017-10-11 6:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 7:30 [patch net-next 0/4] net: sched: get rid of cls_flower->egress_dev Jiri Pirko
2017-10-10 7:30 ` [patch net-next 1/4] net: sched: make tc_action_ops->get_dev return dev and avoid passing net Jiri Pirko
2017-10-10 17:44 ` Cong Wang
2017-10-10 21:19 ` Jiri Pirko
2017-10-11 16:34 ` Cong Wang
2017-10-11 20:43 ` Jiri Pirko
2017-10-10 7:30 ` [patch net-next 2/4] net: sched: introduce per-egress action device callbacks Jiri Pirko
2017-10-10 13:31 ` David Laight
2017-10-10 14:31 ` Jiri Pirko
2017-10-10 15:12 ` David Laight
2017-10-10 15:39 ` Jiri Pirko
2017-10-10 7:30 ` [patch net-next 3/4] net: sched: convert cls_flower->egress_dev users to tc_setup_cb_egdev infra Jiri Pirko
2017-10-10 20:04 ` Or Gerlitz
2017-10-10 20:08 ` Or Gerlitz
2017-10-10 21:16 ` Jiri Pirko
2017-10-10 21:47 ` Or Gerlitz
2017-10-11 8:36 ` Or Gerlitz
2017-10-10 7:30 ` [patch net-next 4/4] net: sched: remove unused tcf_exts_get_dev helper and cls_flower->egress_dev Jiri Pirko
2017-10-10 17:25 ` [patch net-next 0/4] net: sched: get rid of cls_flower->egress_dev Or Gerlitz
[not found] ` <CAJ3xEMgPdcVrogHZmEnH+vP3E53zvEcFN8+wyuEqSs6utHQVRg@mail.gmail.com>
2017-10-10 21:13 ` Jiri Pirko
2017-10-10 21:46 ` Or Gerlitz
2017-10-11 6:44 ` Jiri Pirko [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=20171011064446.GA2039@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=gerlitz.or@gmail.com \
--cc=jhs@mojatatu.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=xiyou.wangcong@gmail.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).