mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: bert hubert <bert.hubert@netherlabs.nl>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: udev regression? lsusb silent (no output) since 2.6.22-rc2 at   least
Date: Sun, 27 May 2007 16:20:17 +0200	[thread overview]
Message-ID: <20070527142017.GA24564@outpost.ds9a.nl> (raw)
In-Reply-To: <1180275001.3131.28.camel@lov.localdomain>

> the separate class device. How does that help text sound?
> 
>   This option provides backward compatibility for systems where
>   usbfs is not mounted, and no udev rule like this exists:
>     SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", \
>       NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0644"

I'm mounting my Linus hat now, but the more I think about the
insta-deprecation of USB_DEVICE_CLASS, and killing lsusb in even a very
recent distribution release, I think this is an ABI or API change.

And we hate those.

So instead of papering this breakage over with cleverly worded help texts
that suggest a solution, how about we set USB_DEVICE_CLASS to 'y' by default
for a few more releases?

It would sure save a lot of lkml traffic on 'lsusb broke!'.

If this is unacceptable, please at least retain the word 'lsusb' somewhere
in the help text, so people have at least the chance to spot their (current)
need for USB_DEVICE_CLASS.

Perhaps:

"Some distributions need this feature for lsusb to work, unless the udev rule
 above is configured".

	Bert

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://netherlabs.nl              Open and Closed source services

  reply	other threads:[~2007-05-27 14:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26 20:18 bert hubert
2007-05-27  2:42 ` Kay Sievers
2007-05-27  9:25   ` bert hubert
2007-05-27 14:10     ` Kay Sievers
2007-05-27 14:20       ` bert hubert [this message]
2007-05-27 14:34         ` Kay Sievers
2007-05-27 14:40           ` bert hubert
2007-05-27  5:37 ` Greg KH

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=20070527142017.GA24564@outpost.ds9a.nl \
    --to=bert.hubert@netherlabs.nl \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®