[PATCH v2 0/8] sparc: use asm-generic/dma-mapping-common.h and pci-dma-compat.h

[FUJITA Tomonori]

This is the second version of the patchset to convert SPARC to
asm-generic/dma-mapping-common.h and pci-dma-compat.h:

http://marc.info/?l=linux-sparc&m=124686094931138&w=2

The changes are:

- I added Arnd's patch (1/8) to remove flush_write_buffers() in
  dma-mapping-common.h. so no need to define useless
  flush_write_buffers() on SPARC.

- I added a patch to remove useless flush_write_buffers() on IA64.

- I found and fixed a bug wrt dma_{alloc|free}_coherent that affects
  pci devices on SPARC32; the bug doesn't use get_dma_ops in
  dma_{alloc|free}_coherent (4/8).

- Robert asked me about the dma-debug feature so I added it (8/8).

- Robert tested [3-8/8] patches. I added 'Tested-by' tags.


This patchset touches multiple architectures so it would be appropriate
to merge it via -mm. However, I think that the changes to IA64 and X86
are not large so it would be easier to merge this via SPARC tree.

=
 arch/ia64/include/asm/dma-mapping.h      |    1 -
 arch/sparc/Kconfig                       |    2 +
 arch/sparc/include/asm/dma-mapping.h     |  145 ++++-------------------
 arch/sparc/include/asm/pci.h             |    3 +
 arch/sparc/include/asm/pci_32.h          |  105 ----------------
 arch/sparc/include/asm/pci_64.h          |   88 --------------
 arch/sparc/kernel/Makefile               |    2 +-
 arch/sparc/kernel/dma.c                  |  175 +--------------------------
 arch/sparc/kernel/dma.h                  |   14 --
 arch/sparc/kernel/iommu.c                |   20 ++-
 arch/sparc/kernel/ioport.c               |  190 ++++++++++++++++-------------
 arch/sparc/kernel/pci.c                  |    2 +-
 arch/sparc/kernel/pci_sun4v.c            |   30 ++----
 arch/x86/kernel/pci-nommu.c              |   27 ++++-
 include/asm-generic/dma-mapping-common.h |    6 -
 15 files changed, 183 insertions(+), 627 deletions(-)



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/