From: Hannes Duerr <h.duerr@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] SPAM: [PATCH pve-network v3 1/4] vnet: do not skip if no range is defined, ask for allocation inside prefix instead
Date: Mon, 7 Apr 2025 17:50:29 +0200 [thread overview]
Message-ID: <fe1b8e5d-28f0-487c-b0c9-3f4f832ecdbb@proxmox.com> (raw)
In-Reply-To: <mailman.181.1734119196.332.pve-devel@lists.proxmox.com>
Tested this patch and the 3 other patches which belong together [0]
Did not run into any issues.
[0]
https://lore.proxmox.com/pve-devel/mailman.183.1734119197.332.pve-devel@lists.proxmox.com/
Please consider this
Tested-by: Hannes Duerr <h.duerr@proxmox.com>
On 12/13/24 20:45, lou lecrivain via pve-devel wrote:
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-04-07 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 19:45 lou lecrivain via pve-devel
2025-04-07 15:50 ` Hannes Duerr [this message]
2025-04-07 16:28 ` [pve-devel] applied: " 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=fe1b8e5d-28f0-487c-b0c9-3f4f832ecdbb@proxmox.com \
--to=h.duerr@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal