Re: [PATCH -mm 3/4] alpha: remove dma_sync_single_range

[Andrew Morton]

On Wed, 3 Feb 2010 23:06:37 -0500 Matt Turner <mattst88@xxxxxxxxx> wrote:

> On Wed, Feb 3, 2010 at 10:13 PM, FUJITA Tomonori
> <fujita.tomonori@xxxxxxxxxxxxx> wrote:
> > dma_sync_single_for_cpu/for_device supports a partial sync so there is
> > no point to have dma_sync_single_range (also dma_sync_single was
> > obsoleted long ago, replaced with dma_sync_single_for_cpu/for_device).
> >
> > There is no user of dma_sync_single_range() in mainline and only Alpha
> > architecture supports dma_sync_single_range(). So it's unlikely that
> > someone out of the tree uses it.
> >
> > Signed-off-by: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
> > Cc: Richard Henderson <rth@xxxxxxxxxxx>
> > Cc: Ivan Kokshaysky <ink@xxxxxxxxxxxxxxxxxxxx>
> > Cc: Matt Turner <mattst88@xxxxxxxxx>
> > ---
> >  arch/alpha/include/asm/dma-mapping.h |    1 -
> >  1 files changed, 0 insertions(+), 1 deletions(-)
> >
> > diff --git a/arch/alpha/include/asm/dma-mapping.h b/arch/alpha/include/asm/dma-mapping.h
> > index 04eb568..f514ede 100644
> > --- a/arch/alpha/include/asm/dma-mapping.h
> > +++ b/arch/alpha/include/asm/dma-mapping.h
> > @@ -59,7 +59,6 @@ int dma_set_mask(struct device *dev, u64 mask);
> >
> >  #define dma_sync_single_for_cpu(dev, addr, size, dir)    ((void)0)
> >  #define dma_sync_single_for_device(dev, addr, size, dir)  ((void)0)
> > -#define dma_sync_single_range(dev, addr, off, size, dir)  ((void)0)
> >  #define dma_sync_sg_for_cpu(dev, sg, nents, dir)         ((void)0)
> >  #define dma_sync_sg_for_device(dev, sg, nents, dir)      ((void)0)
> >  #define dma_cache_sync(dev, va, size, dir)               ((void)0)
> > --
> > 1.5.6.5
> 
> Acked-by: Matt Turner <mattst88@xxxxxxxxx>
> 
> Should I vacuum this one up, or should it go in the -mm tree? I don't
> guess there's much point in sending Linus pull requests for single
> patches.
> 

I'll grab it.
--
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/