All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: dtor_core@ameritech.net, dmitry.torokhov@gmail.com,
	greg@kroah.com, linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] Re: usb: replace __setup("nousb") with __module_param_call
Date: Tue, 3 Jan 2006 12:44:04 -0800	[thread overview]
Message-ID: <20060103124404.213b9257.zaitcev@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0601031530490.18243-100000@iolanthe.rowland.org>

On Tue, 3 Jan 2006 15:34:27 -0500 (EST), Alan Stern <stern@rowland.harvard.edu> wrote:

> > I wish usb-handoff was exported similarly, because there's absolutely
> > no way to tell if it worked or was quietly ignored. And I abhor printks
> > in normal or success cases, so I do not want such indication.
> 
> usb-handoff no longer exists.  The kernel now takes USB host controllers
> away from the BIOS as soon as they are discovered.

This is why I wrote that I wish that it was exposed or exported.
It does not matter now, but it was a good example why the general
policy of exposure may be beneficial. English is very confusing.

-- Pete

      parent reply	other threads:[~2006-01-03 20:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-20 22:15 usb: replace __setup("nousb") with __module_param_call Pete Zaitcev
2005-12-22  6:10 ` Dmitry Torokhov
2005-12-22  8:24   ` Pete Zaitcev
2006-01-03  6:47     ` Dmitry Torokhov
2006-01-03  7:07       ` Pete Zaitcev
2006-01-03 14:46         ` Dmitry Torokhov
2006-01-03 19:35           ` Pete Zaitcev
2006-01-03 20:34             ` [linux-usb-devel] " Alan Stern
2006-01-03 20:38               ` Dmitry Torokhov
2006-01-03 20:52                 ` Alan Stern
2006-01-03 21:04                   ` Dmitry Torokhov
2006-01-03 20:44               ` Pete Zaitcev [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=20060103124404.213b9257.zaitcev@redhat.com \
    --to=zaitcev@redhat.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dtor_core@ameritech.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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.