All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
	davem@davemloft.net, edumazet@google.com, jhs@mojatatu.com,
	xiyou.wangcong@gmail.com, victor@mojatatu.com,
	pctammela@mojatatu.com, idosch@idosch.org, mleitner@redhat.com,
	vladbu@nvidia.com, paulb@nvidia.com
Subject: Re: [patch net-next] net: sched: move block device tracking into tcf_block_get/put_ext()
Date: Fri, 05 Jan 2024 11:20:24 +0000	[thread overview]
Message-ID: <170445362405.9615.14672199227322437246.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240104125844.1522062-1-jiri@resnulli.us>

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Thu,  4 Jan 2024 13:58:44 +0100 you wrote:
> From: Jiri Pirko <jiri@nvidia.com>
> 
> Inserting the device to block xarray in qdisc_create() is not suitable
> place to do this. As it requires use of tcf_block() callback, it causes
> multiple issues. It is called for all qdisc types, which is incorrect.
> 
> So, instead, move it to more suitable place, which is tcf_block_get_ext()
> and make sure it is only done for qdiscs that use block infrastructure
> and also only for blocks which are shared.
> 
> [...]

Here is the summary with links:
  - [net-next] net: sched: move block device tracking into tcf_block_get/put_ext()
    https://git.kernel.org/netdev/net-next/c/94e2557d086a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2024-01-05 11:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 12:58 [patch net-next] net: sched: move block device tracking into tcf_block_get/put_ext() Jiri Pirko
2024-01-04 14:32 ` Ido Schimmel
2024-01-04 16:10 ` Jamal Hadi Salim
2024-01-04 18:03   ` Jiri Pirko
2024-01-04 18:22     ` Jamal Hadi Salim
2024-01-05 11:24       ` Jiri Pirko
2024-01-05 11:51         ` Pedro Tammela
2024-01-06 11:14           ` Jiri Pirko
2024-01-06 11:49             ` Jamal Hadi Salim
2024-01-04 19:26 ` Victor Nogueira
2024-01-04 19:36   ` Jamal Hadi Salim
2024-01-05 11:20 ` patchwork-bot+netdevbpf [this message]
2024-01-10 12:09 ` Ido Schimmel
2024-01-10 14:08   ` Jiri Pirko
2024-01-10 16:17   ` Jiri Pirko
2024-01-11  8:51     ` Ido Schimmel
2024-01-11 15:40   ` Jamal Hadi Salim
2024-01-11 15:42     ` Jamal Hadi Salim
2024-01-11 16:17       ` Petr Machata
2024-01-11 19:55         ` Jamal Hadi Salim
2024-01-11 21:44           ` Petr Machata
2024-01-12 14:47             ` Jamal Hadi Salim
2024-01-12 15:37               ` Petr Machata
2024-01-15 21:02                 ` Jamal Hadi Salim
2024-01-16 10:15                   ` Petr Machata
2024-01-17 20:44                     ` Jamal Hadi Salim
2024-01-19 16:28                       ` Petr Machata
2024-01-21 18:32                         ` Jamal Hadi Salim
2024-01-11 16:27       ` 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=170445362405.9615.14672199227322437246.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@idosch.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=mleitner@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paulb@nvidia.com \
    --cc=pctammela@mojatatu.com \
    --cc=victor@mojatatu.com \
    --cc=vladbu@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.