public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com,
	xiyou.wangcong@gmail.com, mlxsw@mellanox.com, andrew@lunn.ch,
	vivien.didelot@savoirfairelinux.com, f.fainelli@gmail.com,
	michael.chan@broadcom.com, ganeshgr@chelsio.com,
	jeffrey.t.kirsher@intel.com, saeedm@mellanox.com,
	matanb@mellanox.com, leonro@mellanox.com, idosch@mellanox.com,
	jakub.kicinski@netronome.com, simon.horman@netronome.com,
	pieter.jansenvanvuuren@netronome.com, john.hurley@netronome.com,
	alexander.h.duyck@intel.com
Subject: Re: [patch net-next 0/4] net: sched: block callbacks follow-up
Date: Sun, 29 Oct 2017 12:17:14 +0100	[thread overview]
Message-ID: <20171029111714.GB2635@nanopsycho> (raw)
In-Reply-To: <20171029.183632.1515928020513719137.davem@davemloft.net>

Sun, Oct 29, 2017 at 10:36:32AM CET, davem@davemloft.net wrote:
>From: Jiri Pirko <jiri@resnulli.us>
>Date: Wed, 25 Oct 2017 16:34:56 +0200
>
>> 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.
>
>Jiri, this series does not apply cleanly to net-next.

I will respin.


>
>Also, you should really work out the block offload semantics
>with Jakub, continuing the discussion of patch #2.

I have some ideas. I could let driver to enable/disable already
registered callback. Will look at it.

  reply	other threads:[~2017-10-29 11:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25 14:34 [patch net-next 0/4] net: sched: block callbacks follow-up Jiri Pirko
2017-10-25 14:34 ` [patch net-next 1/4] net: sched: remove unused tc_should_offload helper Jiri Pirko
2017-10-25 14:34 ` [patch net-next 2/4] net: sched: move the can_offload check from binding phase to rule insertion phase Jiri Pirko
2017-10-25 22:09   ` Jakub Kicinski
2017-10-26  1:01   ` David Miller
2017-10-26  6:07     ` Jiri Pirko
2017-10-26 15:29       ` Alexander Duyck
2017-10-26 15:40         ` Jiri Pirko
2017-10-26 20:55           ` Jakub Kicinski
2017-10-25 14:34 ` [patch net-next 3/4] net: sched: remove tc_can_offload check from egdev call Jiri Pirko
2017-10-25 14:35 ` [patch net-next 4/4] net: sched: remove ndo_setup_tc check from tc_can_offload Jiri Pirko
2017-10-29  9:36 ` [patch net-next 0/4] net: sched: block callbacks follow-up David Miller
2017-10-29 11:17   ` Jiri Pirko [this message]
2017-11-01 10:41     ` Jiri Pirko

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=20171029111714.GB2635@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=alexander.h.duyck@intel.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=ganeshgr@chelsio.com \
    --cc=idosch@mellanox.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jhs@mojatatu.com \
    --cc=john.hurley@netronome.com \
    --cc=leonro@mellanox.com \
    --cc=matanb@mellanox.com \
    --cc=michael.chan@broadcom.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=pieter.jansenvanvuuren@netronome.com \
    --cc=saeedm@mellanox.com \
    --cc=simon.horman@netronome.com \
    --cc=vivien.didelot@savoirfairelinux.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