Skip to content

RFC mdev-only /dev management (without devtmpfs)

Arnout Vandecappelle buildroot 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest6 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/6Move mounting /sys from fstab to inittab+0 -00 replies
2/6system: clarify /dev management using devtmpfs + {mdev, eudev}+0 -01 reply
2/6system: clarify /dev management using devtmpfs + {mdev, eudev}+0 -00 replies
3/6system: add mdev-only /dev management (without devtmpfs)+0 -016 replies
3/6system: add mdev-only /dev management (without devtmpfs)+0 -01 reply
3/6system: add mdev-only /dev management (without devtmpfs)+0 -00 replies
3/6system: add mdev-only /dev management (without devtmpfs)+0 -01 reply
3/6system: add mdev-only /dev management (without devtmpfs)+0 -01 reply
3/6system: add mdev-only /dev management (without devtmpfs)+0 -01 reply
3/6system: add mdev-only /dev management (without devtmpfs)+0 -04 replies
5/6docs/manual: document "Dynamic using mdev only" /dev management+0 -00 replies

Reviews trailers per patch

10 of 11 patches have a Reviewed-by or Acked-by.

PatchArnout Vandecappelle (Essensium/Mind)John LinnNicolas Pitre
1/6A-b
2/6R-b
2/6R-b
3/6T-b A-b
3/6T-b A-b
3/6T-b A-b
3/6T-b A-b
3/6T-b A-b
3/6T-b A-b
3/6T-b A-b
5/6

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.

Read the v1 thread

Cover letter [Buildroot] [RFC 0/6] mdev-only /dev management (without devtmpfs)
Quoted 7 lines · Luca Ceresoli

There is one rough edge that I'd like to have comments about: variable naming. The new method implemented by this patchset is dynamic and uses mdev, so it should ba named BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV and described in kconfig as "dynamic using mdev". But hey, that name and description are already used for the current "devtmpfs + mdev" method! So we might want to rename all variables to encompass the new use case in a clean way. Thid would also imply lagacy management etc.

Since we don't like legacy management :-) I'd propose to say that DYNAMIC
actually means DEVTMPFS. So the new option would be called BR2_ROOTFS_DEVICE_CREATION_MDEV: it's not devtmpfs, and there's no need for the explicit 'only' part.

What do you think?

Regards,
Arnout

Signature · 6 lines
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF