public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: James.Bottomley@steeleye.com
Cc: linux-arch@vger.kernel.org
Subject: Re: Problem with sg_dma_address() on ia64, sh and sh64
Date: Sat, 20 May 2006 22:55:30 -0700 (PDT)	[thread overview]
Message-ID: <20060520.225530.23952587.davem@davemloft.net> (raw)
In-Reply-To: <1148141933.3529.25.camel@mulgrave.il.steeleye.com>

From: James Bottomley <James.Bottomley@SteelEye.com>
Date: Sat, 20 May 2006 11:18:53 -0500

> This is the defined accessor to our struct scatterlist.  These three
> architectures define it in asm/pci.h rather than asm/scatterlist.h.
> This means that one doesn't get the accessor simply by including
> linux/scatterlist.h, which one should.  This means that non-pci uses
> don't work (like our budding libsrp).
> 
> Could you all move it to where it should be?

I agree, there should be nothing PCI specific about
the scatterlist DMA entry accessors.

      reply	other threads:[~2006-05-21  5:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-20 16:18 Problem with sg_dma_address() on ia64, sh and sh64 James Bottomley
2006-05-21  5:55 ` David S. Miller [this message]

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=20060520.225530.23952587.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-arch@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