NetworkManager/clients
Thomas Haller cd31437024 shared: drop _STATIC variant of macros that define functions
Several macros are used to define function. They had a "_STATIC" variant,
to define the function as static.

I think those macros should not try to abstract entirely what they do.
They should not accept the function scope as argument (or have two
variants per scope). This also because it might make sense to add
additional __attribute__(()) to the function. That only works, if
the macro does not pretend to *not* define a plain function.

Instead, embrace what the function does and let the users place the
function scope as they see fit.

This also follows what is already done with

    static NM_CACHED_QUARK_FCN ("autoconnect-root", autoconnect_root_quark)
2020-02-13 17:17:07 +01:00
..
cli shared: drop _STATIC variant of macros that define functions 2020-02-13 17:17:07 +01:00
cloud-setup shared/trivial: rename time related functions to use "nsec"/"msec" abbreviation instead of "ns"/"ms" 2020-02-10 19:11:50 +01:00
common core: for WireGuard devices use a default dns-priority of 50 (like for VPNs) 2020-02-12 11:55:30 +01:00
tests clients/tests: add test for selecting fields from multiple connections with nmcli con show 2019-12-13 13:19:31 +01:00
tui all: use nm_utils_ipaddr_is_valid() instead of nm_utils_ipaddr_valid() 2020-01-28 11:17:41 +01:00
meson.build nm-online: use nmc_client_new_async() instead of nm_client_new_async() 2019-12-10 09:17:17 +01:00
nm-online.c nm-online: don't fetch permissions for NMClient in nm-online 2019-12-10 09:17:17 +01:00