Re: [PATCH -RFC] moduleparam: introduce core_param_named macro for non-modular code

Paul Gortmaker 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

Re: [PATCH -RFC] moduleparam: introduce core_param_named macro for non-modular code

Paul Gortmaker 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

[PATCH -RFC] moduleparam: introduce core_param_named macro for non-modular code

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%

[PATCH -RFC] moduleparam: introduce core_param_named macro for non-modular code

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%