From: patchwork-bot+netdevbpf@kernel.org
To: Casper Andersson <casper.casan@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, lars.povlsen@microchip.com,
Steen.Hegelund@microchip.com, UNGLinuxDriver@microchip.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3] net: sparx5: Support offloading of bridge port flooding flags
Date: Fri, 25 Feb 2022 05:20:10 +0000 [thread overview]
Message-ID: <164576641016.4654.10769663380687066728.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220223082700.qrot7lepwqcdnyzw@wse-c0155>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 23 Feb 2022 09:27:00 +0100 you wrote:
> Though the SparX-5i can control IPv4/6 multicasts separately from non-IP
> multicasts, these are all muxed onto the bridge's BR_MCAST_FLOOD flag.
>
> Signed-off-by: Casper Andersson <casper.casan@gmail.com>
> Reviewed-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> Changes in v2:
> - Added SWITCHDEV_ATTR_ID_PORT_PRE_BRIDGE_FLAGS callback
> Changes in v3:
> - Removed trailing whitespace
>
> [...]
Here is the summary with links:
- [net-next,v3] net: sparx5: Support offloading of bridge port flooding flags
https://git.kernel.org/netdev/net-next/c/06388a03d2a7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-02-25 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 8:27 [PATCH net-next v3] net: sparx5: Support offloading of bridge port flooding flags Casper Andersson
2022-02-25 5:20 ` 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=164576641016.4654.10769663380687066728.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=casper.casan@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=netdev@vger.kernel.org \
/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.