Paul Gortmaker <paul.gortma...@windriver.com> writes: > We have the case where module_param_named() in file "foo.c" for > parameter myparam translates that into the bootarg for the > non-modular use case as "foo.myparam=..." > > The problem exists where the use case with the filename and the > dot prefix is established, but the code is then realized to be 100% > non-modular, or is converted to non-modular. Both of the existing > macros like core_param() or setup_param() do not append such a > prefix, so a straight conversion to either will break the existing > use cases.
IMHO you should keep using moduleparam. I originally called everything simply param(), but there was a name clash. Linus' answer was basically that "everything is a module, even if it's not a .ko". And it's his tree, so he must be right! Cheers, Rusty.