Good news is that appears to be the only case of this particular usage with MODULE_PARM_DESC Searching for 'blacklist' and MODULE_PARM gives the following:
sound/pci/hda/hda_intel.c:183:MODULE_PARM_DESC(pm_blacklist, "Enable power-management blacklist"); arch/x86/crypto/camellia_glue.c:1473:MODULE_PARM_DESC(force, "Force module load, ignore CPU blacklist"); arch/x86/crypto/twofish_glue_3way.c:251:MODULE_PARM_DESC(force, "Force module load, ignore CPU blacklist"); arch/x86/crypto/des3_ede_glue.c:467:MODULE_PARM_DESC(force, "Force module load, ignore CPU blacklist"); arch/x86/crypto/blowfish_glue.c:423:MODULE_PARM_DESC(force, "Force module load, ignore CPU blacklist"); On Thu, 16 Jul 2020 at 03:45, Paul Schulz <p...@mawsonlakes.org> wrote: > > Yep. +1 for logic > > On Thu, 16 Jul 2020 at 03:11, Jonathan Corbet <cor...@lwn.net> wrote: > > > > On Thu, 16 Jul 2020 01:52:04 +0930 > > Paul Schulz <p...@mawsonlakes.org> wrote: > > > > > -static bool pm_blacklist = true; > > > -module_param(pm_blacklist, bool, 0644); > > > -MODULE_PARM_DESC(pm_blacklist, "Enable power-management blacklist"); > > > +static bool pm_blocklist = true; > > > +module_param(pm_blocklist, bool, 0644); > > > +MODULE_PARM_DESC(pm_blocklist, "Enable power-management blocklist"); > > > > This will break any user specifying this parameter now, which isn't > > something you want to do, methinks... > > > > jon