From: Daniel Golle <daniel@makrotopia.org>
To: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Vignesh Raghavendra <vigneshr@ti.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>
Subject: [PATCH 0/2] ubi: wire up parent device
Date: Thu, 22 Dec 2022 19:32:46 +0000 [thread overview]
Message-ID: <cover.1671737443.git.daniel@makrotopia.org> (raw)
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
--
2.39.0
next reply other threads:[~2022-12-22 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 19:32 Daniel Golle [this message]
2022-12-22 19:33 ` [PATCH 1/2] mtd: ubi: wire-up parent MTD device Daniel Golle
2022-12-22 19:33 ` [PATCH 2/2] mtd: ubi: block: wire-up device parent Daniel Golle
2023-02-14 16:15 ` [PATCH 0/2] ubi: wire up parent device Daniel Golle
2023-02-14 16:21 ` Richard Weinberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1671737443.git.daniel@makrotopia.org \
--to=daniel@makrotopia.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox