public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Torrey Hoffman <thoffman@arnor.net>, vojtech@ucw.cz
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: depmod problem for 2.5.2-dj4
Date: Tue, 22 Jan 2002 20:54:05 -0800	[thread overview]
Message-ID: <20020123045405.GA12060@kroah.com> (raw)
In-Reply-To: <1011744752.2440.0.camel@shire.arnor.net>
In-Reply-To: <1011744752.2440.0.camel@shire.arnor.net>

On Tue, Jan 22, 2002 at 04:12:30PM -0800, Torrey Hoffman wrote:
> 
> depmod: *** Unresolved symbols in
> /lib/modules/2.5.2-dj4/kernel/drivers/usb/hid.o
> depmod: 	usb_make_path
> depmod: *** Unresolved symbols in
> /lib/modules/2.5.2-dj4/kernel/drivers/usb/usbkbd.o
> depmod: 	usb_make_path
> depmod: *** Unresolved symbols in
> /lib/modules/2.5.2-dj4/kernel/drivers/usb/usbmouse.o
> depmod: 	usb_make_path
> make: *** [_modinst_post] Error 1

Looks like you need to add a:
	EXPORT_SYMBOL(usb_make_path);
to the usb.c file.

Vojtech, is this a USB function that you want added to usb.c?
Didn't you (or someone else) propose a function like this in the past?

thanks,

greg k-h

  reply	other threads:[~2002-01-23  4:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-23  0:12 depmod problem for 2.5.2-dj4 Torrey Hoffman
2002-01-23  4:54 ` Greg KH [this message]
2002-01-23  8:44   ` Vojtech Pavlik
2002-01-23 21:24     ` Greg KH
2002-01-23 22:22       ` Greg KH
2002-01-23 22:47         ` Vojtech Pavlik
2002-01-23 23:00           ` Greg KH
2002-01-24  0:46       ` [linux-usb-devel] " David Brownell
2002-01-24  9:01         ` Vojtech Pavlik
2002-01-24  9:20           ` Dave Jones
2002-01-24 15:27           ` [linux-usb-devel] Re: usb+driverfs [was depmod problem for 2.5.2-dj4] David Brownell
2002-01-24 15:32             ` Vojtech Pavlik

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=20020123045405.GA12060@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thoffman@arnor.net \
    --cc=vojtech@ucw.cz \
    /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