All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
	pabeni@redhat.com, f.fainelli@gmail.com, andrew@lunn.ch,
	vivien.didelot@gmail.com, olteanv@gmail.com
Subject: Re: [PATCH net-next 0/6] DSA cross-chip notifier cleanups
Date: Wed, 20 Apr 2022 09:40:12 +0000	[thread overview]
Message-ID: <165044761280.27023.11451310717021718491.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220415154626.345767-1-vladimir.oltean@nxp.com>

Hello:

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

On Fri, 15 Apr 2022 18:46:20 +0300 you wrote:
> This patch set makes the following improvements:
> 
> - Cross-chip notifiers pass a switch index, port index, sometimes tree
>   index, all as integers. Sometimes we need to recover the struct
>   dsa_port based on those integers. That recovery involves traversing a
>   list. By passing directly a pointer to the struct dsa_port we can
>   avoid that, and the indices passed previously can still be obtained
>   from the passed struct dsa_port.
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] net: dsa: move reset of VLAN filtering to dsa_port_switchdev_unsync_attrs
    https://git.kernel.org/netdev/net-next/c/8e9e678e4758
  - [net-next,2/6] net: dsa: make cross-chip notifiers more efficient for host events
    https://git.kernel.org/netdev/net-next/c/726816a129cb
  - [net-next,3/6] net: dsa: use dsa_tree_for_each_user_port in dsa_slave_change_mtu
    https://git.kernel.org/netdev/net-next/c/b2033a05a719
  - [net-next,4/6] net: dsa: avoid one dsa_to_port() in dsa_slave_change_mtu
    https://git.kernel.org/netdev/net-next/c/cf1c39d3b3a5
  - [net-next,5/6] net: dsa: drop dsa_slave_priv from dsa_slave_change_mtu
    https://git.kernel.org/netdev/net-next/c/4715029fa7e9
  - [net-next,6/6] net: dsa: don't emit targeted cross-chip notifiers for MTU change
    https://git.kernel.org/netdev/net-next/c/be6ff9665d64

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



      parent reply	other threads:[~2022-04-20  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 15:46 [PATCH net-next 0/6] DSA cross-chip notifier cleanups Vladimir Oltean
2022-04-15 15:46 ` [PATCH net-next 1/6] net: dsa: move reset of VLAN filtering to dsa_port_switchdev_unsync_attrs Vladimir Oltean
2022-04-15 15:46 ` [PATCH net-next 2/6] net: dsa: make cross-chip notifiers more efficient for host events Vladimir Oltean
2022-04-15 15:46 ` [PATCH net-next 3/6] net: dsa: use dsa_tree_for_each_user_port in dsa_slave_change_mtu Vladimir Oltean
2022-04-15 15:46 ` [PATCH net-next 4/6] net: dsa: avoid one dsa_to_port() " Vladimir Oltean
2022-04-15 15:46 ` [PATCH net-next 5/6] net: dsa: drop dsa_slave_priv from dsa_slave_change_mtu Vladimir Oltean
2022-04-15 15:46 ` [PATCH net-next 6/6] net: dsa: don't emit targeted cross-chip notifiers for MTU change Vladimir Oltean
2022-04-20  9:40 ` patchwork-bot+netdevbpf [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=165044761280.27023.11451310717021718491.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=vivien.didelot@gmail.com \
    --cc=vladimir.oltean@nxp.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.