[DistroKit] [PATCH next v3 4/4] fixup! rauc-udev: generate symlinks based on GPT partition labels

[Roland Hieber <rhi@pengutronix.de>]

Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---

The assumption made in the comment does not hold true, as the fallback
match for mmcblk0p3 conflicts with any possible match made later with
the 'boot_disk' tag a few lines below, so the probe order will influence
the actual target of the symlink and lead to unwanted consequences.
Since we removed the data partition from all genimage configs in a
previous commit ("treewide: images: remove root-B and data partitions"),
the fallback does not match anyway.
---
 projectroot/usr/lib/udev/rules.d/90-rauc-partitions.rules | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/projectroot/usr/lib/udev/rules.d/90-rauc-partitions.rules b/projectroot/usr/lib/udev/rules.d/90-rauc-partitions.rules
index 2da28ae5df16..e2893fa051f9 100644
--- a/projectroot/usr/lib/udev/rules.d/90-rauc-partitions.rules
+++ b/projectroot/usr/lib/udev/rules.d/90-rauc-partitions.rules
@@ -20,10 +20,6 @@ ENV{OF_BASE_COMPATIBLE}=="*radxa,rock3a*", ENV{ID_PATH}=="platform-fe2b0000.mmc"
 # second part: create /dev/disk/by-usage/ symlinks
 ENV{DEVTYPE}!="partition", GOTO="rauc_partitions_end"
 
-# fallback for boards not yet supported by RAUC;
-# this will get overwritten below if we detected the boot disk
-KERNEL=="mmcblk0p3", SYMLINK+="disk/by-usage/data"
-
 # symlinks based on GPT partition labels
 TAGS=="boot_disk", ENV{ID_PART_ENTRY_NAME}=="root-A", SYMLINK+="disk/by-usage/rootfs0"
 TAGS=="boot_disk", ENV{ID_PART_ENTRY_NAME}=="root-B", SYMLINK+="disk/by-usage/rootfs1"
-- 
2.39.2