From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH container v2 2/2] net: drop unused `firewall` argument to add_bridge_fdb()
Date: Wed, 5 Jul 2023 16:38:16 +0200 [thread overview]
Message-ID: <20230705143818.1359775-3-c.heiss@proxmox.com> (raw)
In-Reply-To: <20230705143818.1359775-1-c.heiss@proxmox.com>
PVE::Network::SDN::Zones::add_bridge_fdb() does not actually have a
`firewall` parameter, so drop it.
No functional changes.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
Changes v1 -> v2:
* No changes
src/PVE/LXC.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
index a531ea5..b5bb04b 100644
--- a/src/PVE/LXC.pm
+++ b/src/PVE/LXC.pm
@@ -935,7 +935,7 @@ sub net_tap_plug : prototype($$) {
if ($have_sdn) {
PVE::Network::SDN::Zones::tap_plug($iface, $bridge, $tag, $firewall, $trunks, $rate);
- PVE::Network::SDN::Zones::add_bridge_fdb($iface, $hwaddr, $bridge, $firewall);
+ PVE::Network::SDN::Zones::add_bridge_fdb($iface, $hwaddr, $bridge);
} else {
PVE::Network::tap_plug($iface, $bridge, $tag, $firewall, $trunks, $rate, { mac => $hwaddr });
}
--
2.41.0
next prev parent reply other threads:[~2023-07-05 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 14:38 [pve-devel] [PATCH network/container/qemu-server v2 0/3] drop unused `firewall` argument to {add, del}_bridge_fdb() Christoph Heiss
2023-07-05 14:38 ` [pve-devel] [PATCH network v2 1/1] sdn: zones: " Christoph Heiss
2023-07-05 14:38 ` Christoph Heiss [this message]
2023-07-05 14:38 ` [pve-devel] [PATCH qemu-server v2 3/3] net: " Christoph Heiss
2024-07-22 16:16 ` [pve-devel] [PATCH network/container/qemu-server v2 0/3] " Thomas Lamprecht
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=20230705143818.1359775-3-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pve-devel@lists.proxmox.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 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.