From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Hanreich <s.hanreich@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-network 0/3] Advertise MTU via DHCP / RA
Date: Mon, 22 Apr 2024 14:06:13 +0200 [thread overview]
Message-ID: <ff9ce097-ed00-4357-8766-e8e6aca56b94@proxmox.com> (raw)
In-Reply-To: <20231214164647.435079-1-s.hanreich@proxmox.com>
Am 14/12/2023 um 17:46 schrieb Stefan Hanreich:
> Stefan Hanreich (3):
> dhcp: fix function signatures in abstract class
> zones: add method for getting MTU
> dhcp: dnsmasq: send mtu option via dhcp
>
> src/PVE/Network/SDN/Dhcp.pm | 2 +-
> src/PVE/Network/SDN/Dhcp/Dnsmasq.pm | 7 ++++++-
> src/PVE/Network/SDN/Dhcp/Plugin.pm | 12 ++++++------
> src/PVE/Network/SDN/Zones.pm | 8 ++++++++
> src/PVE/Network/SDN/Zones/Plugin.pm | 7 +++++++
> src/PVE/Network/SDN/Zones/SimplePlugin.pm | 8 +++++++-
> 6 files changed, 35 insertions(+), 9 deletions(-)
>
seems OK from a high-level glance, would need a rebase now though
_______________________________________________
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:[~2024-04-22 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 16:46 Stefan Hanreich
2023-12-14 16:46 ` [pve-devel] [PATCH pve-network 1/3] dhcp: fix function signatures in abstract class Stefan Hanreich
2023-12-14 16:46 ` [pve-devel] [PATCH pve-network 2/3] zones: add method for getting MTU Stefan Hanreich
2023-12-14 16:46 ` [pve-devel] [PATCH pve-network 3/3] dhcp: dnsmasq: send mtu option via dhcp Stefan Hanreich
2024-02-22 13:23 ` [pve-devel] [PATCH pve-network 0/3] Advertise MTU via DHCP / RA Stefan Hanreich
2024-04-22 12:06 ` Thomas Lamprecht [this message]
2024-04-22 13:16 ` Stefan Hanreich
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=ff9ce097-ed00-4357-8766-e8e6aca56b94@proxmox.com \
--to=t.lamprecht@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