From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: [pbs-devel] applied: [PATCH common/proxmox 0/2] Fall back to regex detection for physical nics
Date: Mon, 11 Aug 2025 13:54:19 +0200 [thread overview]
Message-ID: <1754913248.kxsky7argx.astroid@yuna.none> (raw)
In-Reply-To: <20250804111152.271640-1-s.hanreich@proxmox.com>
FTR, this got applied last week..
On August 4, 2025 1:11 pm, Stefan Hanreich wrote:
> To avoid breaking changes in the detection of physical interfaces, use the regex
> in addition to the ip link output.
>
> pve-common:
>
> Stefan Hanreich (1):
> inotify/interfaces: fall back to PHYSICAL_NIC_RE
>
> src/PVE/INotify.pm | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
>
> proxmox:
>
> Stefan Hanreich (1):
> network-api: fall back to PHYSICAL_NIC_REGEX
>
> proxmox-network-api/src/config/helper.rs | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
>
> Summary over all repositories:
> 2 files changed, 7 insertions(+), 3 deletions(-)
>
> --
> Generated by git-murpp 0.8.0
>
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
>
>
>
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2025-08-11 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 11:11 [pbs-devel] " Stefan Hanreich
2025-08-04 11:11 ` [pbs-devel] [PATCH pve-common 1/1] inotify/interfaces: fall back to PHYSICAL_NIC_RE Stefan Hanreich
2025-08-04 11:11 ` [pbs-devel] [PATCH proxmox 1/1] network-api: fall back to PHYSICAL_NIC_REGEX Stefan Hanreich
2025-08-11 11:54 ` Fabian Grünbichler [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=1754913248.kxsky7argx.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=pbs-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