ubi: wire up parent device
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mtd: ubi: wire-up parent MTD devicedrivers/ | +1 | 0 replies | |
| 2/2 | mtd: ubi: block: wire-up device parentdrivers/ drivers/ include/ | +3 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] ubi: wire up parent device
Wire up device parents of UBI devices and ubiblock devices (UBI volume devices are already correctly wired to their parent UBI device). This makes more sense than having UBI devices free-standing in /sys/devices/virtual/ubi/ without any connection to their parent MTD device, and ubiblock devices in /sys/devices/virtual/block/ which would be better hosted by the UBI volume device they belong to.
The purpose of these changes is to allow downstream tools to more easily identify UBI<->hardware relationship, and potentially also improve power management and scheduling performance in future.
Daniel Golle (2):
mtd: ubi: wire-up parent MTD device
mtd: ubi: block: wire-up device parent
drivers/mtd/ubi/block.c | 2 +- drivers/mtd/ubi/build.c | 1 + drivers/mtd/ubi/kapi.c | 1 + include/linux/mtd/ubi.h | 1 + 4 files changed, 4 insertions(+), 1 deletion(-)
base-commit: e45fb347b630ee76482fe938ba76cf8eab811290
Signature · 1 line
2.39.0