All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: grey- and blacklisting drivers [Was: Re: Using the "best available" driver]
Date: Tue, 13 Dec 2005 21:27:42 +0000	[thread overview]
Message-ID: <20051213212742.GA8123@vrfy.org> (raw)
In-Reply-To: <20051207181524.71dc2d41.zaitcev@redhat.com>

On Tue, Dec 13, 2005 at 03:56:49PM -0500, Dmitry Torokhov wrote:
> On 12/13/05, Kay Sievers <kay.sievers@vrfy.org> wrote:
> >
> > And another thing is the prameters textual value like "auto" and
> > "manual". If we never add a third option to it, we may stick with the sysfs
> > boolean, which is smaller and simpler to implement. Not sure what's the
> > best here.
> 
> I prefer textual values because:

> 1. They self-descriptive

The same is true for sysfs booleans. No need to "describe" "autobind" on
and off, right?)

> 2. They already used in kernel, so if you switch to numeric you'll
> break userrspace

Ther are currently no such attributes at the driver level, right? So
this does not apply at all.

> 3. Implementation difference is insignificant.

Well, if a boolean is enough, I disagree. But I'm not sure if someone
will want to specify a third operation mode. Than the textual values
are a big advantage, sure.

Kay


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2005-12-13 21:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08  2:15 grey- and blacklisting drivers [Was: Re: Using the "best Pete Zaitcev
2005-12-08  2:54 ` grey- and blacklisting drivers [Was: Re: Using the "best available" driver] Jean Tourrilhes
2005-12-08 15:31 ` Kay Sievers
2005-12-10  4:20 ` Greg KH
2005-12-11  6:43 ` Kay Sievers
2005-12-11 15:48 ` grey- and blacklisting drivers [Was: Re: Using the "best Pavel Roskin
2005-12-11 16:13 ` grey- and blacklisting drivers [Was: Re: Using the "best available" driver] Kay Sievers
2005-12-11 17:20 ` Dmitry Torokhov
2005-12-11 19:59 ` Dominik Brodowski
2005-12-11 20:00 ` Dominik Brodowski
2005-12-11 20:55 ` Kay Sievers
2005-12-11 21:11 ` Kay Sievers
2005-12-13  4:55 ` Kay Sievers
2005-12-13 19:39 ` Dominik Brodowski
2005-12-13 20:46 ` Kay Sievers
2005-12-13 20:56 ` Dmitry Torokhov
2005-12-13 21:27 ` Kay Sievers [this message]
2005-12-13 22:00 ` Dmitry Torokhov
2005-12-13 22:54 ` Dominik Brodowski
2006-01-08 21:36 ` Dominik Brodowski
2006-01-09  0:44 ` Kay Sievers
2006-01-17 10:51 ` Christian Zoz
  -- strict thread matches above, loose matches on Subject: below --
2005-12-07 21:37 Dominik Brodowski
2005-12-07 22:52 ` Bill Nottingham
2005-12-07 23:07 ` Jean Tourrilhes
2005-12-08  1:23 ` Greg KH
2005-12-08  1:56 ` Jean Tourrilhes

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=20051213212742.GA8123@vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.