public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Greg KH <greg@kroah.com>
Cc: imorgan@webcon.ca, helpdeskie@bencastricum.nl,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.5 Sensors & USB problems
Date: Thu, 6 May 2004 19:41:28 +0200	[thread overview]
Message-ID: <20040506194128.50a37d13.khali@linux-fr.org> (raw)
In-Reply-To: <20040504203738.GJ24802@kroah.com>

> It's not due to the complexity, it's just due to the fact that I
> haven't gotten around to doing it yet :)

OK, I should have stopped guessing and have taken a look to the code
instead.

> Patches to fix this are gladly welcome if the current situation really
> bothers people.  No userspace tools should have a problem with the way
> things are right now.  If they do have problems, please let me know.

You're right, there is no problem, at least no in "production"
environments. The only place where it is somewhat confusing (for
newcomers at least) is when probing the busses in the first time, or for
developers testing bus drivers (but those know what is happening).

At any rate, it is definitely better now than when device and
corresponding adapter could have different numbers. Of course it would
be better if device numbers were reused, but I'm not annoyed enough to
take a look right now either ;)

-- 
Jean Delvare
http://khali.linux-fr.org/

  reply	other threads:[~2004-05-06 17:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 14:56 2.6.5 Sensors & USB problems Jean Delvare
2004-04-17 22:07 ` Ian Morgan
2004-04-17 23:49   ` Ian Morgan
2004-04-18  5:51     ` Jean Delvare
2004-05-04 20:37       ` Greg KH
2004-05-06 17:41         ` Jean Delvare [this message]
2004-04-18  5:32   ` Jean Delvare
  -- strict thread matches above, loose matches on Subject: below --
2004-04-06 16:18 Ben Castricum

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=20040506194128.50a37d13.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=greg@kroah.com \
    --cc=helpdeskie@bencastricum.nl \
    --cc=imorgan@webcon.ca \
    --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