From: David Mosberger <davidm@napali.hpl.hp.com>
To: "David S. Miller" <davem@redhat.com>
Cc: davidm@hpl.hp.com, manfred@colorfullife.com, axboe@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: problem with blk_queue_bounce_limit()
Date: Sat, 7 Jun 2003 00:20:46 -0700 [thread overview]
Message-ID: <16097.37454.827982.278024@napali.hpl.hp.com> (raw)
In-Reply-To: <20030606.234401.104035537.davem@redhat.com>
>>>>> On Fri, 06 Jun 2003 23:44:01 -0700 (PDT), "David S. Miller" <davem@redhat.com> said:
DaveM> This sounds all very dramatic, but try as I might, all I
DaveM> find is three places where PCI_DMA_BUS_IS_PHYS is used:
DaveM> Fix your grep,
What am I missing?
--david
$ find . -type f | xargs fgrep PCI_DMA_BUS_IS_PHYS | fgrep -v /SCCS/
./drivers/ide/ide-lib.c: if (!PCI_DMA_BUS_IS_PHYS)
./drivers/net/tg3.c:#ifndef PCI_DMA_BUS_IS_PHYS
./drivers/net/tg3.c:#define PCI_DMA_BUS_IS_PHYS 1
./drivers/net/tg3.c:#if !PCI_DMA_BUS_IS_PHYS
./drivers/net/tg3.c:#if !PCI_DMA_BUS_IS_PHYS
./drivers/scsi/scsi_lib.c: if (PCI_DMA_BUS_IS_PHYS && host_dev && host_dev->dma_mask)
./include/asm-alpha/pci.h:#define PCI_DMA_BUS_IS_PHYS 0
./include/asm-arm/pci.h:#define PCI_DMA_BUS_IS_PHYS (0)
./include/asm-i386/pci.h:#define PCI_DMA_BUS_IS_PHYS (1)
./include/asm-ia64/pci.h: * PCI_DMA_BUS_IS_PHYS should be set to 1 if there is necessarily a direct corespondence
./include/asm-ia64/pci.h:#define PCI_DMA_BUS_IS_PHYS pci_dma_bus_is_phys
./include/asm-m68k/pci.h:#define PCI_DMA_BUS_IS_PHYS (1)
./include/asm-parisc/pci.h:#define PCI_DMA_BUS_IS_PHYS (1)
./include/asm-ppc/pci.h:#define PCI_DMA_BUS_IS_PHYS (1)
./include/asm-ppc64/pci.h:#define PCI_DMA_BUS_IS_PHYS (0)
./include/asm-s390/pci.h:#define PCI_DMA_BUS_IS_PHYS (1)
./include/asm-sparc/pci.h:#define PCI_DMA_BUS_IS_PHYS (0)
./include/asm-sparc64/pci.h:#define PCI_DMA_BUS_IS_PHYS (0)
./include/asm-um/pci.h:#define PCI_DMA_BUS_IS_PHYS (1)
./include/asm-x86_64/pci.h:#define PCI_DMA_BUS_IS_PHYS (0)
./include/asm-x86_64/pci.h:#define PCI_DMA_BUS_IS_PHYS 1
next prev parent reply other threads:[~2003-06-07 7:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 6:42 David Mosberger
2003-06-05 7:20 ` David S. Miller
2003-06-06 6:42 ` David Mosberger
2003-06-06 6:45 ` David S. Miller
2003-06-06 6:54 ` David Mosberger
2003-06-06 7:08 ` David S. Miller
2003-06-06 6:52 ` David S. Miller
2003-06-06 7:19 ` David Mosberger
2003-06-06 7:32 ` David S. Miller
2003-06-06 7:44 ` Christoph Hellwig
2003-06-06 7:43 ` David S. Miller
2003-06-06 7:51 ` Christoph Hellwig
2003-06-06 20:13 ` David Mosberger
2003-06-07 6:44 ` David S. Miller
2003-06-07 7:05 ` David Mosberger
2003-06-07 7:11 ` David S. Miller
2003-06-10 20:01 ` David Mosberger
2003-06-12 6:47 ` David S. Miller
2003-06-15 7:06 ` Anton Blanchard
2003-06-15 7:11 ` David S. Miller
2003-06-15 8:04 ` Anton Blanchard
2003-06-15 8:18 ` David S. Miller
2003-06-07 7:20 ` David Mosberger [this message]
2003-06-07 7:19 ` David S. Miller
2003-06-07 9:44 ` Russell King
2003-06-07 9:47 ` David S. Miller
2003-06-07 13:23 ` Christoph Hellwig
2003-06-10 20:24 ` David Mosberger
2003-06-06 18:06 James Bottomley
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=16097.37454.827982.278024@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=axboe@suse.de \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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
all inboxes | Powered by JetHome®