From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Gabriel Goller <g.goller@proxmox.com>
Subject: applied: [PATCH ifupdown2] d/patches: don't fail vxlan syntax check on missing local tunnelip
Date: Mon, 2 Nov 2026 21:03:30 +0100 [thread overview]
Message-ID: <179364925011.1243978.16417124016847751620.b4-ty@b4> (raw)
In-Reply-To: <20260914114918.144970-1-g.goller@proxmox.com>
On Mon, 14 Sep 2026 13:49:02 +0200, Gabriel Goller wrote:
> Don't fail the syntax check when no vxlan-local-tunnelip is configured.
> This is fine, the local tunnelip can be retrieved from somewhere else.
> Check the patch description for more info.
>
> We don't usually run `ifreload -s`, so the syntax check won't be run on
> a normal apply.
>
> [...]
Applied, thanks!
Renumbered to 0017, as a new bond patch now takes 0016, fixed the weekday in
the patch's Date header and reworded the paragraph about `ifreload -s` in
the commit message.
[1/1] d/patches: don't fail vxlan syntax check on missing local tunnelip
commit: b88afe4db3fcb7e3f7361a383aeb6e95e04c37ce
prev parent reply other threads:[~2026-11-02 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 11:49 [PATCH ifupdown2] d/patches: don't fail vxlan syntax check on missing local tunnelip Gabriel Goller
2026-11-02 20:03 ` 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=179364925011.1243978.16417124016847751620.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=g.goller@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