public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joseph Pingenot <trelane@digitasaru.net>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Build error on 2.5.20 under unstable debian
Date: Wed, 5 Jun 2002 12:21:29 -0500	[thread overview]
Message-ID: <20020605122129.A14027@ksu.edu> (raw)
In-Reply-To: <23055.1023262706@kao2.melbourne.sgi.com> <Pine.NEB.4.44.0206050958190.9994-100000@mimas.fachschaften.tu-muenchen.de>

>From Adrian Bunk on Wednesday, 05 June, 2002:
>On Wed, 5 Jun 2002, Keith Owens wrote:
>uhci_stop is __devexit but the pointer to it doesn't use __devexit_p.
>The fix is simple:
>--- drivers/usb/host/uhci-hcd.c.old	Wed Jun  5 09:59:00 2002
>+++ drivers/usb/host/uhci-hcd.c	Wed Jun  5 10:13:09 2002
>@@ -2515,7 +2515,7 @@
> 	suspend:		uhci_suspend,
> 	resume:			uhci_resume,
> #endif
>-	stop:			uhci_stop,
>+	stop:			__devexit_p(uhci_stop),
>
> 	hcd_alloc:		uhci_hcd_alloc,
> 	hcd_free:		uhci_hcd_free,

Ah.  What does __devexit_p() do?  It looks to be some sort of macro,
  doing a cast?
And thanks, the patch solved the problem.  I'm currently running 2.5.20. :)

-Joseph
-- 
Joseph======================================================jap3003@ksu.edu
"Ich bin ein Penguin."  --/. poster mmarlett, responding to news that the
  Bundestag will move to IBM/SuSE Linux.  
                      http://slashdot.org/comments.pl?sid=33588&cid=3631032

  reply	other threads:[~2002-06-05 17:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 15:36 Build error on 2.5.20 under unstable debian Joseph Pingenot
2002-06-04 22:28 ` Joseph Pingenot
2002-06-05  1:39 ` Keith Owens
2002-06-05  7:25   ` Joseph Pingenot
2002-06-05  7:38     ` Keith Owens
2002-06-05  8:18       ` Adrian Bunk
2002-06-05 17:21         ` Joseph Pingenot [this message]
2002-06-05 20:08           ` Adrian Bunk
2002-06-05 18:41         ` 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=20020605122129.A14027@ksu.edu \
    --to=trelane@digitasaru.net \
    --cc=bunk@fs.tum.de \
    --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