All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Matching semantics for version numbers....
Date: Wed, 21 Mar 2001 06:12:09 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98515556703877@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98512282728951@msgid-missing>

Hi Matt,

Two comments come to mind:

(1) Is it correct that changing this would involve no more than:

* Linux 2.4.? kernel updates:
    - drivers/usb/usb.c ... usb_match_id()
    - drivers/usb/ibmcam.c ... uses range matching
    - drivers/usb/storage/unusual_devs.h ... lots of ranges
* Hotplug scripts
* "usbmodules"
* No spec/documentation (yet)

Distributions would need to get all those updates at once;
I don't know how much of a problem that'd be, except
that if there's no coordination then it'll be painful.  If it
happens, this should all be ready at the same time.  (Not
like the original match_flags patch ... though goofing this
up would break less, since "modutils" will still work.)

(2) For some reason my preference in this area would
be to use "low <= value < high" range specs rather the
current "low < value < high" or "low <= value <= high".

That's just a better match to how I normally think about
such ranges -- not a huge deal, but it seems like Jeff
Ozvold had a similar thought.  So maybe I'm not alone
in thinking about those bcd version codes that way.

- Dave




_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2001-03-21  6:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-20 21:12 Matching semantics for version numbers Matthew Dharm
2001-03-21  6:12 ` David Brownell [this message]
2001-03-21 18:54 ` Matthew Dharm
2001-03-22 19:23 ` David Brownell
2001-03-22 19:50 ` Matthew Dharm

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=marc-linux-hotplug-98515556703877@msgid-missing \
    --to=david-b@pacbell.net \
    --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.