linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Jes Sorensen <jes@sgi.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	Matthew Wilcox <matthew@wil.cx>,
	linux-arch@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Removal of dma_cache_* functions?
Date: Tue, 11 Sep 2007 14:58:17 +0100	[thread overview]
Message-ID: <20070911135817.GA1285@linux-mips.org> (raw)
In-Reply-To: <yq0sl5le2p2.fsf@jaguar.mkp.net>

On Tue, Sep 11, 2007 at 09:44:57AM -0400, Jes Sorensen wrote:

> Only issue I could think off would be the m68k drivers, but I don't
> know if that ever migrated to the MIPS API or stayed with the old m68k
> one - Geert and comments?

That would only apply to out of tree drivers.  With the patch applied
git grep -E -w -l 'dma_cache_(wback|wback_inv|inv)' only finds:

arch/mips/au1000/common/dbdma.c
arch/mips/jazz/jazzdma.c
arch/mips/mm/dma-default.c
drivers/net/sgiseeq.c
drivers/scsi/dec_esp.c
include/asm-mips/floppy.h
include/asm-mips/io.h

For sgiseeq there already is a patch in flight.

  Ralf

  reply	other threads:[~2007-09-11 13:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-04 11:56 Removal of dma_cache_* functions? Ralf Baechle
2007-09-04 12:42 ` Matthew Wilcox
2007-09-04 12:57   ` James Bottomley
2007-09-04 13:07     ` Ralf Baechle
2007-09-04 23:49       ` James Bottomley
2007-09-11 13:44       ` Jes Sorensen
2007-09-11 13:58         ` Ralf Baechle [this message]
2007-09-04 13:07     ` Matthew Wilcox
2007-09-04 13:33       ` Ralf Baechle
2007-09-06 11:39   ` [PATCH] Removal of dma_cache_(wback|inv|wback_inv) functions Ralf Baechle
2007-09-06 14:55     ` Paul Mackerras
2007-09-06 15:02     ` David Miller
2007-09-06 15:02     ` Kyle McMartin
2007-09-06 21:28     ` Håvard Skinnemoen

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=20070911135817.GA1285@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=geert@linux-m68k.org \
    --cc=jes@sgi.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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;
as well as URLs for NNTP newsgroup(s).