[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171101153133.x5agqnsvjss2rnga@netronome.com>
Date: Wed, 1 Nov 2017 16:31:34 +0100
From: Simon Horman <simon.horman@...ronome.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, davem@...emloft.net, nogahf@...lanox.com,
jhs@...atatu.com, xiyou.wangcong@...il.com, mlxsw@...lanox.com,
andrew@...n.ch, vivien.didelot@...oirfairelinux.com,
f.fainelli@...il.com, michael.chan@...adcom.com,
ganeshgr@...lsio.com, saeedm@...lanox.com, matanb@...lanox.com,
leonro@...lanox.com, idosch@...lanox.com,
jakub.kicinski@...ronome.com, pieter.jansenvanvuuren@...ronome.com,
john.hurley@...ronome.com, alexander.h.duyck@...el.com,
ogerlitz@...lanox.com, john.fastabend@...il.com
Subject: Re: [patch net-next RFC 2/9] net_sch: mqprio: Change TC_SETUP_MQPRIO
to TC_SETUP_QDISC_MQPRIO
On Mon, Oct 30, 2017 at 09:56:06AM +0100, Jiri Pirko wrote:
> From: Nogah Frankel <nogahf@...lanox.com>
>
> Change TC_SETUP_MQPRIO to TC_SETUP_QDISC_MQPRIO to match the new
> convention.
Why is there a new convention? This churn in this and the following patch
warrant some justification IMHO.
Powered by blists - more mailing lists