From: David Riley <d.riley@proxmox.com>
To: Stefan Hanreich <s.hanreich@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH access-control/network 0/2] fix #7520: sdn: clean up dangling ACLs on resource deletion
Date: Mon, 18 May 2026 11:49:26 +0200 [thread overview]
Message-ID: <68160669-1341-4682-8bc4-ff8a4ddea201@proxmox.com> (raw)
In-Reply-To: <0472cd7e-4610-488c-80db-5b41a2e70c65@proxmox.com>
Thanks for taking a look.
I will be sending out a v2 with your suggestions.
On 5/7/26 3:01 PM, Stefan Hanreich wrote:
> Thanks for the series!
>
> Would it be possible to send a v2 that also includes route-maps and
> prefix-lists?
>
> [...]
prev parent reply other threads:[~2026-05-18 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 14:22 [PATCH access-control/network 0/2] fix #7520: sdn: clean up dangling ACLs on resource deletion David Riley
2026-05-05 14:22 ` [PATCH pve-network 1/2] " David Riley
2026-05-05 14:22 ` [PATCH pve-access-control 2/2] fix #7520: access-control: add SDN ACL cleanup helper David Riley
2026-05-07 13:03 ` [PATCH access-control/network 0/2] fix #7520: sdn: clean up dangling ACLs on resource deletion Stefan Hanreich
2026-05-18 9:49 ` David Riley [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=68160669-1341-4682-8bc4-ff8a4ddea201@proxmox.com \
--to=d.riley@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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