From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, kuba@kernel.org, linux@armlinux.org.uk,
f.fainelli@gmail.com, vivien.didelot@gmail.com,
vladimir.oltean@nxp.com, andrew@lunn.ch
Subject: Re: [PATCH net-next] net: lan966x: Add support for multiple bridge flags
Date: Thu, 23 Dec 2021 11:20:09 +0000 [thread overview]
Message-ID: <164025840979.28761.13346033254282858520.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211222110759.1404383-1-horatiu.vultur@microchip.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 22 Dec 2021 12:07:59 +0100 you wrote:
> This patch series extends the current supported bridge flags with the
> following flags: BR_FLOOD, BR_BCAST_FLOOD and BR_LEARNING.
>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> .../ethernet/microchip/lan966x/lan966x_main.c | 7 ++
> .../ethernet/microchip/lan966x/lan966x_main.h | 2 +
> .../ethernet/microchip/lan966x/lan966x_regs.h | 6 ++
> .../microchip/lan966x/lan966x_switchdev.c | 69 ++++++++++++++++++-
> 4 files changed, 82 insertions(+), 2 deletions(-)
Here is the summary with links:
- [net-next] net: lan966x: Add support for multiple bridge flags
https://git.kernel.org/netdev/net-next/c/2e49761e4fd1
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:[~2021-12-23 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 11:07 [PATCH net-next] net: lan966x: Add support for multiple bridge flags Horatiu Vultur
2021-12-23 11: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=164025840979.28761.13346033254282858520.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=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox