Skip to content

RFC mdev-only /dev management (without devtmpfs)

Thomas Petazzoni 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
3/6system: add mdev-only /dev management (without devtmpfs)+0 -00 replies
3/6system: add mdev-only /dev management (without devtmpfs)+0 -03 replies
3/6system: add mdev-only /dev management (without devtmpfs)+0 -04 replies
3/6system: add mdev-only /dev management (without devtmpfs)+0 -02 replies
3/6system: add mdev-only /dev management (without devtmpfs)+0 -01 reply
3/6system: add mdev-only /dev management (without devtmpfs)+0 -04 replies
3/6system: add mdev-only /dev management (without devtmpfs)+0 -07 replies
3/6system: add mdev-only /dev management (without devtmpfs)+0 -01 reply

Reviews trailers per patch

All 8 patches have a Reviewed-by or Acked-by.

PatchJohn LinnNicolas Pitre
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
3/6T-b A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [Buildroot] [RFC 0/6] mdev-only /dev management (without devtmpfs)

Hello,

Quoted 9 lines · Arnout Vandecappelle
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.

Quoted 6 lines

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?

I agree. I would prefer to not change the name of existing options.

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com