public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Proper fix for sym53c8xx_2 driver and dma64_addr_t
Date: Tue, 05 Feb 2002 21:44:06 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805996@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805991@msgid-missing>

>>>>> On Tue, 5 Feb 2002 22:38:04 +0100, Christoph Hellwig <hch@caldera.de> said:

  Christoph> On Tue, Feb 05, 2002 at 12:43:17PM -0800, Michael Madore
  Christoph> wrote:
  >> Hi,
  >> 
  >> Back in early december, it was brought up that eh sym53c8xx_2
  >> driver makes use of dma64_addr_t, which is not defined on IA64.
  >> I got the impression that it was the driver that needed to be
  >> modified to correct the problem, but I don't recall seeing a
  >> specific solution.  I was going to simply replace dma64_addr_t
  >> with u64 in sym_glue.c for now.  Is there a better way?

  Christoph> IA64 needs to define dma64_addr_t.

Not before the driver writers understand when to use it.

	--david


  parent reply	other threads:[~2002-02-05 21:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 20:43 [Linux-ia64] Proper fix for sym53c8xx_2 driver and dma64_addr_t Michael Madore
2002-02-05 21:23 ` Gérard Roudier
2002-02-05 21:26 ` David Mosberger
2002-02-05 21:34 ` Gérard Roudier
2002-02-05 21:38 ` Christoph Hellwig
2002-02-05 21:44 ` David Mosberger [this message]
2002-02-06  8:21 ` Christoph Hellwig
2002-02-06  8:29 ` David S. Miller
2002-02-06  8:35 ` Christoph Hellwig
2002-02-06  8:45 ` David S. Miller
2002-02-06 16:54 ` David Mosberger
2002-02-06 17:10 ` Christoph Hellwig
2002-02-06 17:15 ` Christoph Hellwig
2002-02-06 17:15 ` David Mosberger
2002-02-06 21:38 ` Gérard Roudier
2002-02-07  2:09 ` David S. Miller

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=marc-linux-ia64-105590698805996@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@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