From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Subject: [pve-devel] applied-series: [PATCH pve-network 0/4] add disable bridge learning feature
Date: Wed, 16 Mar 2022 16:41:44 +0100 [thread overview]
Message-ID: <1aa24ad2-c469-7f39-7f5b-6b9b2c16023a@proxmox.com> (raw)
In-Reply-To: <20210924085101.3078775-1-aderumier@odiso.com>
On 24.09.21 10:50, Alexandre Derumier wrote:
> following pve-common
> https://lists.proxmox.com/pipermail/pve-devel/2021-September/050090.html
>
> Alexandre Derumier (4):
> vnets: fix get_vnet
> zones : tap_plug: add support for disable bridge learning
> zones: add add_bridge_fdb
> zones: add del_bridge_fdb
>
> PVE/Network/SDN/Vnets.pm | 8 ++++----
> PVE/Network/SDN/Zones.pm | 32 ++++++++++++++++++++++++++++-
> PVE/Network/SDN/Zones/Plugin.pm | 2 +-
> PVE/Network/SDN/Zones/QinQPlugin.pm | 1 +
> PVE/Network/SDN/Zones/VlanPlugin.pm | 5 +++++
> 5 files changed, 42 insertions(+), 6 deletions(-)
>
applied series, thanks!
It's to long ago (sorry) but the related container/qemu-server patches require
a pve-common change that's not yet applied or?
prev parent reply other threads:[~2022-03-16 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 8:50 [pve-devel] " Alexandre Derumier
2021-09-24 8:50 ` [pve-devel] [PATCH pve-network 1/4] vnets: fix get_vnet Alexandre Derumier
2021-09-24 8:50 ` [pve-devel] [PATCH pve-network 2/4] zones : tap_plug: add support for disable bridge learning Alexandre Derumier
2021-09-24 8:51 ` [pve-devel] [PATCH pve-network 3/4] zones: add add_bridge_fdb Alexandre Derumier
2021-09-24 8:51 ` [pve-devel] [PATCH pve-network 4/4] zones: add del_bridge_fdb Alexandre Derumier
2022-03-16 15:41 ` Thomas Lamprecht [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=1aa24ad2-c469-7f39-7f5b-6b9b2c16023a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=aderumier@odiso.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox