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

Hi!

I've only recently noticed that this series is marked as 'Accepted' in
patchwork. However, I fail to find the commits in any public linux
tree, nor has patchwork sent the usual notification email informing me
about it being accepted.

Can it be that it has slipped under the table (or even the carpet)
somehow?

Please let me know if there is anything wrong with this series and/or
if I should re-submit it, or if I shall just wait for it to surface in
linux-mtd or linux-next.


Thank you!


Best regards


Daniel


On Thu, Dec 22, 2022 at 07:32:46PM +0000, Daniel Golle wrote:
> 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
> 
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

----- Ursprüngliche Mail -----
> I've only recently noticed that this series is marked as 'Accepted' in
> patchwork. However, I fail to find the commits in any public linux
> tree, nor has patchwork sent the usual notification email informing me
> about it being accepted.
> 
> Can it be that it has slipped under the table (or even the carpet)
> somehow?
> 
> Please let me know if there is anything wrong with this series and/or
> if I should re-submit it, or if I shall just wait for it to surface in
> linux-mtd or linux-next.

The patches are in linux-ubifs #next and in linux-next itself.
See:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=05b8773ca33253ea562be145cf3145b05ef19f86

So, all good. :-)
 
Thanks,
//richard