From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH common 0/4] fix #5141: fix parsing of explicit vlan devices
Date: Thu, 21 Dec 2023 16:30:21 +0100 [thread overview]
Message-ID: <20231221153025.678700-1-f.gruenbichler@proxmox.com> (raw)
patches 1 and 2 are just to make writing the test case in 4 possible in the
first place. 3 is the actual fix.
Fabian Grünbichler (4):
network tests: switch to ifupdown2
network parser: iterate deterministically
fix #5141: network parser: fix accidental RE result re-use
network tests: test #5141
src/PVE/INotify.pm | 21 ++++++--
test/etc_network_interfaces/runtest.pl | 2 +-
.../t.bridge_eth_remove_auto.pl | 24 ---------
.../t.create_network.pl | 6 +--
.../t.ovs_bridge_allow.pl | 12 ++---
test/etc_network_interfaces/t.vlan-parsing.pl | 54 +++++++++++++++++++
6 files changed, 80 insertions(+), 39 deletions(-)
delete mode 100644 test/etc_network_interfaces/t.bridge_eth_remove_auto.pl
create mode 100644 test/etc_network_interfaces/t.vlan-parsing.pl
--
2.39.2
next reply other threads:[~2023-12-21 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 15:30 Fabian Grünbichler [this message]
2023-12-21 15:30 ` [pve-devel] [PATCH common 1/4] network tests: switch to ifupdown2 Fabian Grünbichler
2023-12-21 15:30 ` [pve-devel] [PATCH common 2/4] network parser: iterate deterministically Fabian Grünbichler
2023-12-21 15:30 ` [pve-devel] [PATCH common 3/4] fix #5141: network parser: fix accidental RE result re-use Fabian Grünbichler
2023-12-21 15:30 ` [pve-devel] [PATCH common 4/4] network tests: test #5141 Fabian Grünbichler
2024-01-03 11:19 ` [pve-devel] applied: [PATCH common 0/4] fix #5141: fix parsing of explicit vlan devices Wolfgang Bumiller
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=20231221153025.678700-1-f.gruenbichler@proxmox.com \
--to=f.gruenbichler@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox