public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	UNGLinuxDriver@microchip.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	linux@armlinux.org.uk, vladimir.oltean@nxp.com
Subject: Re: [PATCH net-next v4 0/8] net: lan966x: Add lag support
Date: Mon, 22 Aug 2022 13:30:16 +0000	[thread overview]
Message-ID: <166117501692.5977.2992380067711592787.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220817193449.1673002-1-horatiu.vultur@microchip.com>

Hello:

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

On Wed, 17 Aug 2022 21:34:41 +0200 you wrote:
> Add lag support for lan966x.
> First 4 patches don't do any changes to the current behaviour, they
> just prepare for lag support. While the rest is to add the lag support.
> 
> v3->v4:
> - aggregation configuration is global for all bonds, so make sure that
>   there can't be enabled multiple configurations at the same time
> - return error faster from lan966x_foreign_bridging_check, don't
>   continue the search if the error is seen already
> - flush fdb workqueue when a port leaves a bridge or lag.
> 
> [...]

Here is the summary with links:
  - [net-next,v4,1/8] net: lan966x: Add registers used to configure lag interfaces
    https://git.kernel.org/netdev/net-next/c/7c300735a1a1
  - [net-next,v4,2/8] net: lan966x: Split lan966x_fdb_event_work
    https://git.kernel.org/netdev/net-next/c/9b4ed7d262f3
  - [net-next,v4,3/8] net: lan966x: Flush fdb workqueue when port is leaving a bridge.
    https://git.kernel.org/netdev/net-next/c/86bac7f11788
  - [net-next,v4,4/8] net: lan966x: Expose lan966x_switchdev_nb and lan966x_switchdev_blocking_nb
    https://git.kernel.org/netdev/net-next/c/d6208adfc9a9
  - [net-next,v4,5/8] net: lan966x: Extend lan966x_foreign_bridging_check
    https://git.kernel.org/netdev/net-next/c/a751ea4d74e9
  - [net-next,v4,6/8] net: lan966x: Add lag support for lan966x
    https://git.kernel.org/netdev/net-next/c/cabc9d49333d
  - [net-next,v4,7/8] net: lan966x: Extend FDB to support also lag
    https://git.kernel.org/netdev/net-next/c/9be99f2d1d28
  - [net-next,v4,8/8] net: lan966x: Extend MAC to support also lag interfaces.
    https://git.kernel.org/netdev/net-next/c/e09ce97778e8

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-08-22 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 19:34 [PATCH net-next v4 0/8] net: lan966x: Add lag support Horatiu Vultur
2022-08-17 19:34 ` [PATCH net-next v4 1/8] net: lan966x: Add registers used to configure lag interfaces Horatiu Vultur
2022-08-17 19:34 ` [PATCH net-next v4 2/8] net: lan966x: Split lan966x_fdb_event_work Horatiu Vultur
2022-08-17 19:34 ` [PATCH net-next v4 3/8] net: lan966x: Flush fdb workqueue when port is leaving a bridge Horatiu Vultur
2022-08-17 19:34 ` [PATCH net-next v4 4/8] net: lan966x: Expose lan966x_switchdev_nb and lan966x_switchdev_blocking_nb Horatiu Vultur
2022-08-17 19:34 ` [PATCH net-next v4 5/8] net: lan966x: Extend lan966x_foreign_bridging_check Horatiu Vultur
2022-08-17 19:34 ` [PATCH net-next v4 6/8] net: lan966x: Add lag support for lan966x Horatiu Vultur
2022-08-17 19:34 ` [PATCH net-next v4 7/8] net: lan966x: Extend FDB to support also lag Horatiu Vultur
2022-08-17 19:34 ` [PATCH net-next v4 8/8] net: lan966x: Extend MAC to support also lag interfaces Horatiu Vultur
2022-08-22 13:30 ` 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=166117501692.5977.2992380067711592787.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox