diff options
author | Thomas Haller <thaller@redhat.com> | 2020-02-12 15:02:46 +0100 |
---|---|---|
committer | Thomas Haller <thaller@redhat.com> | 2020-02-17 14:43:13 +0100 |
commit | 4c101f36eca3e71c5d11e0175cd38d50c4ae5dfa (patch) | |
tree | ff9199b3e975868a8f242047bbed6648b8a3ec37 /src/dhcp/nm-dhcp-client.h | |
parent | be4129bb2db90b1a03d8dd45e7c5ea9c0f9e6f7b (diff) | |
download | NetworkManager-4c101f36eca3e71c5d11e0175cd38d50c4ae5dfa.tar.gz |
device: don't schedule grace timeout if dhcp-timeout is infinity
It feels wrong to schedule a timeout with G_MAXUINT32, if we actually
disabled the timeout. Of course, in practice there should be little
difference.
Diffstat (limited to 'src/dhcp/nm-dhcp-client.h')
-rw-r--r-- | src/dhcp/nm-dhcp-client.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/dhcp/nm-dhcp-client.h b/src/dhcp/nm-dhcp-client.h index 884de85040..1ff09067e8 100644 --- a/src/dhcp/nm-dhcp-client.h +++ b/src/dhcp/nm-dhcp-client.h @@ -12,8 +12,8 @@ #include "nm-ip6-config.h" #include "nm-dhcp-utils.h" -#define NM_DHCP_TIMEOUT_DEFAULT ((guint32) 45) /* default DHCP timeout, in seconds */ -#define NM_DHCP_TIMEOUT_INFINITY G_MAXINT32 +#define NM_DHCP_TIMEOUT_DEFAULT ((guint32) 45) /* default DHCP timeout, in seconds */ +#define NM_DHCP_TIMEOUT_INFINITY ((guint32) G_MAXINT32) #define NM_TYPE_DHCP_CLIENT (nm_dhcp_client_get_type ()) #define NM_DHCP_CLIENT(obj) (G_TYPE_CHECK_INSTANCE_CAST ((obj), NM_TYPE_DHCP_CLIENT, NMDhcpClient)) |