From: Takashi Iwai <tiwai@suse.de>
To: Paul Schulz <paul@mawsonlakes.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>
Subject: Re: [PATCH] sound/pci/hda: Changes 'blacklist/whitelist' to 'blocklist/allowlist'
Date: Thu, 16 Jul 2020 09:03:45 +0200 [thread overview]
Message-ID: <s5h7dv4osa6.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAGt04nZLViVautnbeFFMbx=_=0eNbW3fz5AAVKi6wCXDHZn2rA@mail.gmail.com>
On Wed, 15 Jul 2020 20:45:43 +0200,
Paul Schulz wrote:
>
> 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");
Note that the blacklist/whitelist words have been already replaced in
sound/*, while this module option name was left intact for
compatibility.
At the next time, please include the proper subsystem ML to Cc.
thanks,
Takashi
> 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 <paul@mawsonlakes.org> wrote:
> >
> > Yep. +1 for logic
> >
> > On Thu, 16 Jul 2020 at 03:11, Jonathan Corbet <corbet@lwn.net> wrote:
> > >
> > > On Thu, 16 Jul 2020 01:52:04 +0930
> > > Paul Schulz <paul@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
>
prev parent reply other threads:[~2020-07-16 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 16:22 [PATCH] sound/pci/hda: Changes 'blacklist/whitelist' to 'blocklist/allowlist' Paul Schulz
2020-07-15 17:40 ` Jonathan Corbet
2020-07-15 18:15 ` Paul Schulz
2020-07-15 18:45 ` Paul Schulz
2020-07-16 7:03 ` Takashi Iwai [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5h7dv4osa6.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@mawsonlakes.org \
--cc=perex@perex.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox