netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, roopa@nvidia.com,
	nikolay@nvidia.com, jiri@nvidia.com, idosch@nvidia.com,
	kuba@kernel.org, lkp@intel.com
Subject: Re: [PATCH net-next] net: bridge: switchdev: fix shim definition for br_switchdev_mdb_notify
Date: Sat, 30 Oct 2021 04:40:08 +0000	[thread overview]
Message-ID: <163556880800.10957.12949174206170467469.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211029223606.3450523-1-vladimir.oltean@nxp.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Sat, 30 Oct 2021 01:36:06 +0300 you wrote:
> br_switchdev_mdb_notify() is conditionally compiled only when
> CONFIG_NET_SWITCHDEV=y and CONFIG_BRIDGE_IGMP_SNOOPING=y. It is called
> from br_mdb.c, which is conditionally compiled only when
> CONFIG_BRIDGE_IGMP_SNOOPING=y.
> 
> The shim definition of br_switchdev_mdb_notify() is therefore needed for
> the case where CONFIG_NET_SWITCHDEV=n, however we mistakenly put it
> there for the case where CONFIG_BRIDGE_IGMP_SNOOPING=n. This results in
> build failures when CONFIG_BRIDGE_IGMP_SNOOPING=y and
> CONFIG_NET_SWITCHDEV=n.
> 
> [...]

Here is the summary with links:
  - [net-next] net: bridge: switchdev: fix shim definition for br_switchdev_mdb_notify
    https://git.kernel.org/netdev/net-next/c/ae0393500e3b

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



      reply	other threads:[~2021-10-30  4:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 22:36 [PATCH net-next] net: bridge: switchdev: fix shim definition for br_switchdev_mdb_notify Vladimir Oltean
2021-10-30  4: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=163556880800.10957.12949174206170467469.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=idosch@nvidia.com \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@nvidia.com \
    --cc=roopa@nvidia.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;
as well as URLs for NNTP newsgroup(s).