From: patchwork-bot+netdevbpf@kernel.org
To: Vadym Kochan <vadym.kochan@plvision.eu>
Cc: volodymyr.mytnyk@plvision.eu, andrii.savka@plvision.eu,
davem@davemloft.net, kuba@kernel.org,
oleksandr.mazur@plvision.eu, serhiy.boiko@plvision.eu,
serhiy.pshyk@plvision.eu, taras.chornyi@plvision.eu,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
mickeyr@marvell.com
Subject: Re: [PATCH net] net: marvell: prestera: fix compilation with CONFIG_BRIDGE=m
Date: Sat, 07 Nov 2020 20:50:05 +0000 [thread overview]
Message-ID: <160478220549.18540.15454874231670042478.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201106161128.24069-1-vadym.kochan@plvision.eu>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 6 Nov 2020 18:11:25 +0200 you wrote:
> With CONFIG_BRIDGE=m the compilation fails:
>
> ld: drivers/net/ethernet/marvell/prestera/prestera_switchdev.o: in function `prestera_bridge_port_event':
> prestera_switchdev.c:(.text+0x2ebd): undefined reference to `br_vlan_enabled'
>
> in case the driver is statically enabled.
>
> [...]
Here is the summary with links:
- [net] net: marvell: prestera: fix compilation with CONFIG_BRIDGE=m
https://git.kernel.org/netdev/net/c/4e0396c59559
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:[~2020-11-07 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 16:11 [PATCH net] net: marvell: prestera: fix compilation with CONFIG_BRIDGE=m Vadym Kochan
2020-11-06 20:13 ` Randy Dunlap
2020-11-07 20:45 ` Jakub Kicinski
2020-11-07 20:50 ` 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=160478220549.18540.15454874231670042478.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.savka@plvision.eu \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mickeyr@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=oleksandr.mazur@plvision.eu \
--cc=serhiy.boiko@plvision.eu \
--cc=serhiy.pshyk@plvision.eu \
--cc=taras.chornyi@plvision.eu \
--cc=vadym.kochan@plvision.eu \
--cc=volodymyr.mytnyk@plvision.eu \
/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.