From: Jens Axboe <axboe@suse.de>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@redhat.com>
Subject: Re: [patch] block highmem zero bounce v14
Date: Sat, 22 Sep 2001 13:00:00 +0200 [thread overview]
Message-ID: <20010922130000.A632@suse.de> (raw)
In-Reply-To: <20010916234307.A12270@suse.de> <Pine.LNX.4.33.0109161447390.29507-100000@penguin.transmeta.com> <20010917000012.B12270@suse.de> <20010921114448.D1924@devserv.devel.redhat.com>
In-Reply-To: <20010921114448.D1924@devserv.devel.redhat.com>
On Fri, Sep 21 2001, Arjan van de Ven wrote:
> On Mon, Sep 17, 2001 at 12:00:12AM +0200, Jens Axboe wrote:
> > On Sun, Sep 16 2001, Linus Torvalds wrote:
> > >
> > > On Sun, 16 Sep 2001, Jens Axboe wrote:
> > > >
> > > > It's against 2.4.10-pre9 and can be found right here:
> > > >
> > > > *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.10-pre9/block-highmem-all-14
> > >
> > > Jens, what's your feeling about the stability of these things, especially
> > > wrt weird drivers?
> >
> > One of the very first decisions I made wrt this patch was to make sure
> > that weird/old drivers could keep on working exactly the way they do now
> > and never have to worry about highmem stuff.
>
> unfortionatly, so far both megaraid and the 3ware driver broke. Megaraid is
> easily fixable, but still. It shows that this patch is not without risk...
megaraid broke because can_dma_32 was enabled by mistake.
jens
next prev parent reply other threads:[~2001-09-22 11:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-16 21:43 [patch] block highmem zero bounce v14 Jens Axboe
2001-09-16 21:48 ` Linus Torvalds
2001-09-16 22:00 ` Jens Axboe
2001-09-16 23:10 ` Alan Cox
2001-09-16 23:13 ` Jens Axboe
2001-09-21 15:44 ` Arjan van de Ven
2001-09-21 16:13 ` Alan Cox
2001-09-21 16:39 ` spurious interrupt with ac kernel but not with vanilla 2.4.9 Luigi Genoni
2001-09-21 17:03 ` Alan Cox
2001-09-21 17:14 ` Luigi Genoni
2001-09-21 17:28 ` Alan Cox
2001-09-21 17:33 ` Luigi Genoni
2001-09-22 14:39 ` John Levon
2001-09-22 11:00 ` Jens Axboe [this message]
2001-09-22 11:18 ` [patch] block highmem zero bounce v14 Arjan van de Ven
2001-09-22 12:11 ` Jens Axboe
2001-09-22 16:32 ` Alan Cox
2001-09-22 16:35 ` Jens Axboe
2001-09-22 16:41 ` Alan Cox
2001-09-22 16:56 ` Jens Axboe
2001-09-22 17:05 ` Arnaldo Carvalho de Melo
2001-09-20 23:43 ` David S. Miller
2001-09-21 5: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=20010922130000.A632@suse.de \
--to=axboe@suse.de \
--cc=arjanv@redhat.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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