From: "David S. Miller" <davem@redhat.com>
To: torvalds@transmeta.com
Cc: axboe@suse.de, linux-kernel@vger.kernel.org, arjanv@redhat.com
Subject: Re: [patch] block highmem zero bounce v14
Date: Thu, 20 Sep 2001 16:43:01 -0700 (PDT) [thread overview]
Message-ID: <20010920.164301.76328081.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109161447390.29507-100000@penguin.transmeta.com>
In-Reply-To: <20010916234307.A12270@suse.de> <Pine.LNX.4.33.0109161447390.29507-100000@penguin.transmeta.com>
From: Linus Torvalds <torvalds@transmeta.com>
Date: Sun, 16 Sep 2001 14:48:32 -0700 (PDT)
Jens, what's your feeling about the stability of these things, especially
wrt weird drivers?
Ie do you think this is really a 2.4.x thing, or early 2.5.x?
On my side of this work I feel that the 64-bit PCI dma infrastructure
by itself is a safe merge in 2.4.11 or something like that.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-09-20 23:43 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 ` [patch] block highmem zero bounce v14 Jens Axboe
2001-09-22 11:18 ` 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 [this message]
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=20010920.164301.76328081.davem@redhat.com \
--to=davem@redhat.com \
--cc=arjanv@redhat.com \
--cc=axboe@suse.de \
--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