From: Jens Axboe <axboe@suse.de>
To: Sir Ace <chandleg@wizardsworks.org>, linux-scsi@vger.kernel.org
Subject: Re: Maybe a patch?
Date: Wed, 22 Jan 2003 08:59:43 +0100 [thread overview]
Message-ID: <20030122075943.GW20780@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0301211606060.27122-100000@wizardsworks.org>
On Tue, Jan 21 2003, Sir Ace wrote:
>
> I saw in /usr/src/linux/drivers/net/tg3.c
> That the following was added... I have no idea why..
> Like I said I am not a developer nor do I know a lot about this part of
> the kernel. But it now compiles:
>
> Added to /usr/src/linux/drivers/scsi/scsi_merge.c
>
> #ifndef PCI_DMA_BUS_IS_PHYS
> #define PCI_DMA_BUS_IS_PHYS 1
> #endif
Please don't do stuff like that, it _could_ be dangerous to your data
when you don't know what you are doing.
That said, it is correct for hppa it seems. asm/pci.h has the same
thing, do you are just looking at a missing include. You should fix that
instead. page_to_phys() is also there.
--
Jens Axboe
next prev parent reply other threads:[~2003-01-22 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 0:08 Maybe a patch? Sir Ace
2003-01-22 7:59 ` Jens Axboe [this message]
2003-01-22 18:32 ` Sir Ace
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=20030122075943.GW20780@suse.de \
--to=axboe@suse.de \
--cc=chandleg@wizardsworks.org \
--cc=linux-scsi@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