linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Jonathan Masters <jcm@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	Lucas De Marchi <lucas.demarchi@profusion.mobi>,
	Andy Lutomirski <luto@amacapital.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ben Hutchings <bhutchings@solarflare.com>,
	"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>
Subject: Re: [RFC PATCH] Allow optional module parameters
Date: Wed, 03 Jul 2013 23:03:41 +0200	[thread overview]
Message-ID: <51D491AD.7050008@suse.cz> (raw)
In-Reply-To: <9F26321B-7088-4D16-80D5-72EB388F8E49@redhat.com>

Dne 1.7.2013 18:33, Jonathan Masters napsal(a):
> One caveat. Sometimes we have manufactured parameters intentionally
> to cause a module to fail. We should standardize that piece.

You have:

  blacklist foo

to prevent udev from loading a module and

  install foo /bin/true

to prevent modprobe from loading the module at all. What is the
motivation for inventing a third way, through adding invalid parameters?

Thanks,
Michal

  parent reply	other threads:[~2013-07-03 21:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 20:07 [RFC PATCH] Allow optional module parameters Andy Lutomirski
2013-03-15  5:03 ` Rusty Russell
2013-03-15 18:18   ` Andy Lutomirski
2013-03-18  2:24     ` Rusty Russell
2013-03-18 17:42       ` Andy Lutomirski
2013-03-19  2:32         ` Rusty Russell
2013-03-19 19:40           ` Ben Hutchings
2013-03-20  2:31             ` Rusty Russell
2013-03-20  0:26           ` Lucas De Marchi
2013-03-20  0:32             ` Andy Lutomirski
2013-03-20  0:36               ` Andy Lutomirski
2013-03-20  3:45             ` Rusty Russell
2013-07-01  6:50               ` Rusty Russell
2013-07-01 16:33                 ` Jonathan Masters
2013-07-03  0:28                   ` Rusty Russell
2013-07-03 21:03                   ` Michal Marek [this message]
2013-07-03 21:17                     ` Andy Lutomirski
2013-07-03 21:23                       ` Michal Marek
2013-07-03 21:30                         ` Yann E. MORIN
2013-07-03 21:31                         ` Lucas De Marchi
2013-07-03 21:36                           ` Andy Lutomirski

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=51D491AD.7050008@suse.cz \
    --to=mmarek@suse.cz \
    --cc=bhutchings@solarflare.com \
    --cc=jcm@redhat.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.demarchi@profusion.mobi \
    --cc=luto@amacapital.net \
    --cc=rusty@rustcorp.com.au \
    /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;
as well as URLs for NNTP newsgroup(s).