From: Arjan van de Ven <arjanv@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: arjanv@redhat.com, jes@wildopensource.com,
torvalds@transmeta.com, James.Bottomley@steeleye.com,
grundler@dsl2.external.hp.com, cngam@sgi.com, jeremy@sgi.com,
linux-kernel@vger.kernel.org, linux-ia64@linuxia64.org,
wildos@sgi.com
Subject: Re: [patch] support 64 bit pci_alloc_consistent
Date: Sun, 18 May 2003 09:43:41 +0000 [thread overview]
Message-ID: <20030518094341.A1709@devserv.devel.redhat.com> (raw)
In-Reply-To: <20030518.023533.98888328.davem@redhat.com>; from davem@redhat.com on Sun, May 18, 2003 at 02:35:33AM -0700
On Sun, May 18, 2003 at 02:35:33AM -0700, David S. Miller wrote:
> WHile logically you are correct, the probing code is going to
> look basically identical.
For most drivers I don't think it will. Most drivers will just say "look I
can do THIS much. I don't give a flying fish about how much of
that you actually use". At least in the probing code.
In code of say a scsi driver that has to pick some dma descriptor format it's a different
matter of course, but there you have to check SOMETHING, either a variable
you stored during probing, or now the effective mask....
next prev parent reply other threads:[~2003-05-18 9:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-18 4:09 [patch] support 64 bit pci_alloc_consistent Jes Sorensen
2003-05-18 5:46 ` David S. Miller
2003-05-18 6:00 ` Andre Hedrick
2003-05-18 9:29 ` Arjan van de Ven
2003-05-18 9:35 ` David S. Miller
2003-05-18 9:43 ` Arjan van de Ven [this message]
2003-05-18 17:22 ` [Linux-ia64] " Grant Grundler
2003-05-18 17:49 ` James Bottomley
2003-05-18 20:17 ` Grant Grundler
2003-05-18 21:26 ` James Bottomley
2003-05-19 16:26 ` Grant Grundler
2003-05-18 14:17 ` James Bottomley
2003-05-18 14:21 ` Arjan van de Ven
2003-05-18 14:28 ` James Bottomley
[not found] <mailman.1053231184.22467.linux-kernel2news@redhat.com>
2003-05-18 7:05 ` Pete Zaitcev
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=20030518094341.A1709@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=James.Bottomley@steeleye.com \
--cc=cngam@sgi.com \
--cc=davem@redhat.com \
--cc=grundler@dsl2.external.hp.com \
--cc=jeremy@sgi.com \
--cc=jes@wildopensource.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=wildos@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.