Prev: [PATCH -V16 07/12] vfs: Support null pathname in linkat
Next: [PATCH -V16 09/12] x86: Add new syscalls for x86_64
From: FUJITA Tomonori on 12 Jul 2010 02:40 On Mon, 12 Jul 2010 15:37:20 +0900 FUJITA Tomonori <fujita.tomonori(a)lab.ntt.co.jp> wrote: > HAVE_ARCH_PCI_SET_DMA_MASK was removed in 2.6.36 (no architecture has Oops, HAVE_ARCH_PCI_SET_DMA_MASK was removed in 2.6.34. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Michal Simek on 12 Jul 2010 09:20
FUJITA Tomonori wrote: > HAVE_ARCH_PCI_SET_DMA_MASK was removed in 2.6.36 (no architecture has > the own implementation of pci_set_dma_mask). Added to next branch. I also fixed that kernel version. Thanks, Michal > > Signed-off-by: FUJITA Tomonori <fujita.tomonori(a)lab.ntt.co.jp> > --- > arch/microblaze/include/asm/dma-mapping.h | 6 ------ > 1 files changed, 0 insertions(+), 6 deletions(-) > > diff --git a/arch/microblaze/include/asm/dma-mapping.h b/arch/microblaze/include/asm/dma-mapping.h > index 18b3731..5073895 100644 > --- a/arch/microblaze/include/asm/dma-mapping.h > +++ b/arch/microblaze/include/asm/dma-mapping.h > @@ -79,12 +79,6 @@ static inline int dma_supported(struct device *dev, u64 mask) > return ops->dma_supported(dev, mask); > } > > -#ifdef CONFIG_PCI > -/* We have our own implementation of pci_set_dma_mask() */ > -#define HAVE_ARCH_PCI_SET_DMA_MASK > - > -#endif > - > static inline int dma_set_mask(struct device *dev, u64 dma_mask) > { > struct dma_map_ops *ops = get_dma_ops(dev); -- Michal Simek, Ing. (M.Eng) w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/ Microblaze U-BOOT custodian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |