1 files changed, 15 insertions, 15 deletions

diff --git a/src/nm-netns.c b/src/nm-netns.c
index f07bb1c498..b4e28fa3ab 100644
--- a/src/nm-netns.c
+++ b/src/nm-netns.c
@@ -179,12 +179,12 @@ _platform_signal_on_idle_cb(gpointer user_data)
     priv->signal_pending_idle_id = 0;
 
     /* we emit all queued signals together. However, we don't want to hook the
-	 * main loop for longer than the currently queued elements.
-	 *
-	 * If we catch more change events, they will be queued and processed by a future
-	 * idle handler.
-	 *
-	 * Hence, move the list to a temporary list. Isn't CList great? */
+     * main loop for longer than the currently queued elements.
+     *
+     * If we catch more change events, they will be queued and processed by a future
+     * idle handler.
+     *
+     * Hence, move the list to a temporary list. Isn't CList great? */
 
     c_list_init(&work_list);
     c_list_splice(&work_list, &priv->l3cfg_signal_pending_lst_head);
@@ -385,21 +385,21 @@ constructed(GObject *object)
     priv->rules_manager = nmp_rules_manager_new(priv->platform);
 
     /* Weakly track the default rules with a dummy user-tag. These
-	 * rules are always weekly tracked... */
+     * rules are always weekly tracked... */
     nmp_rules_manager_track_default(priv->rules_manager,
                                     AF_UNSPEC,
                                     0,
                                     nm_netns_parent_class /* static dummy user-tag */);
 
     /* Also weakly track all existing rules. These were added before NetworkManager
-	 * starts, so they are probably none of NetworkManager's business.
-	 *
-	 * However note that during service restart, devices may stay up and rules kept.
-	 * That means, after restart such rules may have been added by a previous run
-	 * of NetworkManager, we just don't know.
-	 *
-	 * For that reason, whenever we will touch such rules later one, we make them
-	 * fully owned and no longer weekly tracked. See %NMP_RULES_MANAGER_EXTERN_WEAKLY_TRACKED_USER_TAG. */
+     * starts, so they are probably none of NetworkManager's business.
+     *
+     * However note that during service restart, devices may stay up and rules kept.
+     * That means, after restart such rules may have been added by a previous run
+     * of NetworkManager, we just don't know.
+     *
+     * For that reason, whenever we will touch such rules later one, we make them
+     * fully owned and no longer weekly tracked. See %NMP_RULES_MANAGER_EXTERN_WEAKLY_TRACKED_USER_TAG. */
     nmp_rules_manager_track_from_platform(priv->rules_manager,
                                           NULL,
                                           AF_UNSPEC,