From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Cc: linux-usb-devel@lists.sourceforge.net
Subject: Re: Announce: modutils 2.4.0 is available
Date: Fri, 05 Jan 2001 14:56:29 +1100 [thread overview]
Message-ID: <16062.978666989@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Fri, 05 Jan 2001 13:59:12 +1100." <14993.978663552@kao2.melbourne.sgi.com>
On Fri, 05 Jan 2001 13:59:12 +1100,
Keith Owens <kaos@ocs.com.au> wrote:
>modutils-2.4.0.tar.gz Source tarball, includes RPM spec file
I have just found out that there was an incompatible change to struct
usb_device_id during 2.4.0-prerelease :(((. That means that all
versions of depmod will break on kernel 2.4.0 if you have any modules
that use MODULE_DEVICE_TABLE(usb). Incompatible changes to an ABI
structure without notification immediately prior to a major kernel
release, yech!
If you have usb modules then stay on kernel 2.4.0-prerelease or compile
usb without modules or wait until I can test and release modutils
2.4.1. The usb hotplug utilities will also have to change to handle
the new table layout.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-05 3:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 2:59 Announce: modutils 2.4.0 is available Keith Owens
2001-01-05 3:56 ` Keith Owens [this message]
2001-01-05 4:03 ` Matthew Dharm
2001-01-05 4:54 ` [linux-usb-devel] " David Brownell
2001-01-05 5:56 ` Matthew Dharm
2001-01-05 7:07 ` Greg KH
[not found] ` <3A55751D.4020800@megapathdsl.net>
2001-01-05 7:30 ` Greg KH
2001-01-05 8:28 ` Matti Aarnio
2001-01-05 6:55 ` Miles Lane
2001-01-05 6:48 ` Anuradha Ratnaweera
2001-01-05 10:31 ` Erik Mouw
2001-01-05 15:31 ` Wichert Akkerman
2001-01-05 16:10 ` Anuradha Ratnaweera
2001-01-05 19:33 ` Russell King
2001-01-08 12:41 ` Peter Samuelson
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=16062.978666989@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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