sched/balancing: Change comment formatting to not overlap Git conflict marker lines
authorIngo Molnar <mingo@kernel.org>
Fri, 8 Mar 2024 10:58:57 +0000 (11:58 +0100)
committerIngo Molnar <mingo@kernel.org>
Tue, 12 Mar 2024 10:03:41 +0000 (11:03 +0100)
So the scheduler has two such comment blocks, with '=' used as a double underline:

        /*
         * VRUNTIME
         * ========
         *

'========' also happens to be a Git conflict marker, throwing off a simple
search in an editor for this pattern.

Change them to '-------' type of underline instead - it looks just as good.

Signed-off-by: Ingo Molnar <mingo@kernel.org>
Reviewed-by: Valentin Schneider <vschneid@redhat.com>
Reviewed-by: Vincent Guittot <vincent.guittot@linaro.org>
Link: https://lore.kernel.org/r/20240308105901.1096078-7-mingo@kernel.org
kernel/sched/fair.c

index 3a510cf1fb0063176598ab9aaadb6f641d9ed419..84d4791cf628b5bbbb8bbbd2960b9a671da11b40 100644 (file)
@@ -3679,7 +3679,7 @@ static void reweight_eevdf(struct cfs_rq *cfs_rq, struct sched_entity *se,
 
        /*
         * VRUNTIME
-        * ========
+        * --------
         *
         * COROLLARY #1: The virtual runtime of the entity needs to be
         * adjusted if re-weight at !0-lag point.
@@ -3762,7 +3762,7 @@ static void reweight_eevdf(struct cfs_rq *cfs_rq, struct sched_entity *se,
 
        /*
         * DEADLINE
-        * ========
+        * --------
         *
         * When the weight changes, the virtual time slope changes and
         * we should adjust the relative virtual deadline accordingly.