mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager
synced 2024-10-14 12:05:03 +00:00
all: codespell fixes
Codespel run with the same arguments as described in
commit 58510ed566
('docs: misc. typos pt2').
This commit is contained in:
parent
7811d1c187
commit
3c6644db32
|
@ -208,7 +208,7 @@ _value_strsplit (const char *value,
|
|||
gsize len;
|
||||
|
||||
/* FIXME: some modes should support backslash escaping.
|
||||
* In particular, to distingish from _value_str_as_index_list(), which
|
||||
* In particular, to distinguish from _value_str_as_index_list(), which
|
||||
* does not accept '\\'. */
|
||||
|
||||
/* note that all modes remove empty tokens (",", "a,,b", ",,"). */
|
||||
|
@ -3398,7 +3398,7 @@ _objlist_set_fcn_ip_config_routing_rules (NMSetting *setting,
|
|||
return FALSE;
|
||||
|
||||
/* also for @do_add, we first always search whether such a rule already exist
|
||||
* and remove the first occurance.
|
||||
* and remove the first occurrence.
|
||||
*
|
||||
* The effect is, that we don't add multiple times the same rule,
|
||||
* and that if the rule already exists, it gets moved to the end (append).
|
||||
|
|
|
@ -110,7 +110,7 @@
|
|||
%global config_plugins_default ifcfg-rh
|
||||
|
||||
%if 0%{?fedora}
|
||||
# Altough eBPF would be available on Fedora's kernel, it seems
|
||||
# Although eBPF would be available on Fedora's kernel, it seems
|
||||
# we often get SELinux denials (rh#1651654). But even aside them,
|
||||
# bpf(BPF_MAP_CREATE, ...) randomly fails with EPERM. That might
|
||||
# be related to `ulimit -l`. Anyway, this is not usable at the
|
||||
|
|
|
@ -1627,7 +1627,7 @@ nm_ip_routing_rule_is_sealed (const NMIPRoutingRule *self)
|
|||
* @self: the #NMIPRoutingRule instance
|
||||
*
|
||||
* Seals the routing rule. Afterwards, the instance can no longer be
|
||||
* modfied, and it is a bug to call any of the accessors that would
|
||||
* modified, and it is a bug to call any of the accessors that would
|
||||
* modify the rule. If @self was already sealed, this has no effect.
|
||||
*
|
||||
* Since: 1.18
|
||||
|
@ -2214,7 +2214,7 @@ nm_ip_routing_rule_get_xifname_bin (const NMIPRoutingRule *self,
|
|||
* The name supports C backslash escaping for non-UTF-8 characters.
|
||||
* Note that nm_ip_routing_rule_from_string() too uses backslash
|
||||
* escaping when tokenizing the words by whitespace. So, in string
|
||||
* representation you'd get double backslashs.
|
||||
* representation you'd get double backslashes.
|
||||
*
|
||||
* Since: 1.18
|
||||
*/
|
||||
|
@ -2251,7 +2251,7 @@ nm_ip_routing_rule_get_oifname (const NMIPRoutingRule *self)
|
|||
* The name supports C backslash escaping for non-UTF-8 characters.
|
||||
* Note that nm_ip_routing_rule_from_string() too uses backslash
|
||||
* escaping when tokenizing the words by whitespace. So, in string
|
||||
* representation you'd get double backslashs.
|
||||
* representation you'd get double backslashes.
|
||||
*
|
||||
* Since: 1.18
|
||||
*/
|
||||
|
|
|
@ -81,7 +81,7 @@ typedef struct {
|
|||
* But it will not remove or add them otherwise.
|
||||
*
|
||||
* Otherwise, the track_priority_val goes together with track_priority_present.
|
||||
* In case of one rule being tracked multile times (with different priorities),
|
||||
* In case of one rule being tracked multiple times (with different priorities),
|
||||
* the one with higher priority wins. See _rules_obj_get_best_data().
|
||||
* Then, the winning present state either enforces that the rule is present
|
||||
* or absent.
|
||||
|
|
Loading…
Reference in a new issue