From 22f401b269e867ef5255660dc052217f85187be6 Mon Sep 17 00:00:00 2001
From: Lennart Poettering <lennart@poettering.net>
Date: Mon, 14 Sep 2020 12:59:38 +0200
Subject: [PATCH] unit-def: drop pointless 0 initialization of first enum value

This is implied in C and we generally don't bother with this, so don't
bother with this here either.
---
 src/basic/unit-def.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/basic/unit-def.h b/src/basic/unit-def.h
index 53419ecd8a1..1fab6c78ab1 100644
--- a/src/basic/unit-def.h
+++ b/src/basic/unit-def.h
@@ -9,7 +9,7 @@
  * when other criteria (cpu weight, nice level) are identical.
  * In this case service units have the highest priority. */
 typedef enum UnitType {
-        UNIT_SERVICE = 0,
+        UNIT_SERVICE,
         UNIT_MOUNT,
         UNIT_SWAP,
         UNIT_SOCKET,
@@ -25,7 +25,7 @@ typedef enum UnitType {
 } UnitType;
 
 typedef enum UnitLoadState {
-        UNIT_STUB = 0,
+        UNIT_STUB,
         UNIT_LOADED,
         UNIT_NOT_FOUND,    /* error condition #1: unit file not found */
         UNIT_BAD_SETTING,  /* error condition #2: we couldn't parse some essential unit file setting */
-- 
2.47.3