[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20171102.161218.1843909398891251556.davem@davemloft.net>
Date: Thu, 02 Nov 2017 16:12:18 +0900 (KST)
From: David Miller <davem@...emloft.net>
To: jiri@...nulli.us
Cc: netdev@...r.kernel.org, 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,
simon.horman@...ronome.com, pieter.jansenvanvuuren@...ronome.com,
john.hurley@...ronome.com, alexander.h.duyck@...el.com
Subject: Re: [patch net-next v2 0/4] net: sched: block callbacks follow-up
From: Jiri Pirko <jiri@...nulli.us>
Date: Wed, 1 Nov 2017 11:47:37 +0100
> From: Jiri Pirko <jiri@...lanox.com>
>
> This patchset does a bit of cleanup of leftovers after block callbacks
> patchset. The main part is patch 2, which restores the original handling
> of tc offload feature flag.
>
> ---
> v1->v2:
> - rebased on top of current net-next (bnxt changes)
Series applied, thanks Jiri.
Powered by blists - more mailing lists