From: Andries Brouwer <aebr@win.tue.nl>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] 2.4 IDE core for 2.5, #2 (was Re: [PATCH] 2.4 IDE core for 2.5)
Date: Fri, 12 Jul 2002 13:06:20 +0200 [thread overview]
Message-ID: <20020712110620.GA14338@win.tue.nl> (raw)
In-Reply-To: <20020710111115.GJ3185@suse.de>
On Wed, Jul 10, 2002 at 01:11:15PM +0200, Jens Axboe wrote:
> Care to try the next version? I've completely disabled task file i/o
> since it does seem to be broken in pio, and fixed the multi-write
> multi-page bio bug as well. There are a number of other changes in
> there. There are split patches like last time, but also one big patch:
>
> *.kernel.org/pub/linux/kernel/people/axboe/patches/v2.5/2.5.25/
>
> ide24-for-2.5-2
> all of the above
Had no time until now, but just tried ide24-for-2.5-3.
It did not compile, but after adding 05_25pci-ids-1a it did.
Also added
diff -u --recursive --new-file -X /linux/dontdiff a/drivers/usb/host/uhci-hcd.c b/drivers/usb/host/uhci-hcd.c
--- a/drivers/usb/host/uhci-hcd.c Mon Jun 17 19:35:40 2002
+++ b/drivers/usb/host/uhci-hcd.c Fri Jun 21 22:44:35 2002
@@ -2428,7 +2428,7 @@
return retval;
}
-static void __devexit uhci_stop(struct usb_hcd *hcd)
+static void uhci_stop(struct usb_hcd *hcd)
{
struct uhci_hcd *uhci = hcd_to_uhci(hcd);
@@ -2509,7 +2509,7 @@
suspend: uhci_suspend,
resume: uhci_resume,
#endif
- stop: __devexit_p(uhci_stop),
+ stop: uhci_stop,
hcd_alloc: uhci_hcd_alloc,
hcd_free: uhci_hcd_free,
to prevent oopses at shutdown.
The resulting kernel seems to work. Tried it only for a short time,
but maybe long enough to be confident.
[Yesterday, or the day before I installed a new distribution.
Unfortunately there are vendor modifications to kernel and
user space software, so replacing the kernel by a vanilla one
does not yield a functioning system; will also have to replace
some vendor user space stuff by vanilla stuff.]
Andries
next prev parent reply other threads:[~2002-07-12 11:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 10:22 [PATCH] 2.4 IDE core for 2.5 Jens Axboe
2002-07-09 10:48 ` Anton Altaparmakov
2002-07-09 10:49 ` Jens Axboe
2002-07-09 10:51 ` Vojtech Pavlik
2002-07-09 10:53 ` Jens Axboe
2002-07-09 11:17 ` Jens Axboe
2002-07-09 12:52 ` Bartlomiej Zolnierkiewicz
2002-07-09 12:56 ` Jens Axboe
2002-07-09 13:13 ` Bartlomiej Zolnierkiewicz
[not found] ` <Pine.SOL.4.30.0207091510450.28198-100000@mion.elka.pw.edu.pl>
2002-07-09 13:16 ` Jens Axboe
2002-07-09 11:11 ` Erik Andersen
2002-07-09 11:13 ` Roy Sigurd Karlsbakk
[not found] ` <200207091313.07199.roy@karlsbakk.net>
2002-07-09 11:20 ` Jens Axboe
2002-07-09 21:43 ` Miles Lane
2002-07-09 11:24 ` Thunder from the hill
2002-07-09 12:43 ` Tobias Rittweiler
2002-07-09 12:48 ` Jens Axboe
2002-07-09 12:54 ` Jens Axboe
2002-07-09 13:31 ` Re[3]: " Tobias Rittweiler
[not found] ` <20020709124827.GA1940@suse.de>
2002-07-09 12:57 ` Re[2]: " Tobias Rittweiler
2002-07-09 20:07 ` Andries Brouwer
2002-07-10 5:43 ` Jens Axboe
2002-07-10 11:11 ` [PATCH] 2.4 IDE core for 2.5, #2 (was Re: [PATCH] 2.4 IDE core for 2.5) Jens Axboe
2002-07-12 11:06 ` Andries Brouwer [this message]
2002-07-12 11:23 ` IDE Anders Widman
2002-07-11 9:54 ` [PATCH] 2.4 IDE core for 2.5 Rogier Wolff
2002-07-11 9:56 ` Jens Axboe
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=20020712110620.GA14338@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=axboe@suse.de \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).