Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1213637

Re: xtensa build failures in -next due to DMA API changes

From Andrew Morton <akpm@linux-foundation.org>
Newsgroups linux.kernel
Subject Re: xtensa build failures in -next due to DMA API changes
Date 2015-08-26 10:00 +0200
Message-ID <q1DMK-7Vl-17@gated-at.bofh.it> (permalink)
References <q1sHD-7Q-3@gated-at.bofh.it> <q1sRk-ky-19@gated-at.bofh.it> <q1t10-vU-17@gated-at.bofh.it> <q1t10-vU-15@gated-at.bofh.it> <q1DMK-7Vl-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Wed, 26 Aug 2015 10:53:25 +0300 Max Filippov <jcmvbkbc@gmail.com> wrote:

> On Tue, Aug 25, 2015 at 11:24 PM, Christoph Hellwig <hch@lst.de> wrote:
> > On Tue, Aug 25, 2015 at 01:21:40PM -0700, Guenter Roeck wrote:
> >> I also see
> >>
> >> arch/xtensa/include/asm/dma-mapping.h:#include <asm-generic/dma-mapping-common.h>
> >>
> >> It looks like there is a conflict with "xtensa: reimplement DMA API using common
> >> helpers" by Max Filippov, which added the include. This patch is in -next.
> >
> > Oh.  That one clashes badly with my whole series, basically each
> > of my patches will need the same work done for the other architectures
> > applied to xtensa as well.
> >
> > In terms of effort it might be a better idea to rebase the patch from
> > Max on top of the series, as it will become a lot simpler that way.
> 
> Looks like I just need to remove now redundant function definitions from
> xtensa/include/asm/dma-mapping.h. A patch that removes these
> functions is attached, but I'm not sure where it should go. To the Andrew's
> tree? Or should the xtensa tree merge Christoph's series and apply it on
> top?

I can add it to Christoph's patch series.  This means that I won't be
merging Christoph's patches until you've sent your queue in to Linus, so
please don't leave it too late in the merge window.

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

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

xtensa build failures in -next due to DMA API changes Guenter Roeck <linux@roeck-us.net> - 2015-08-25 22:10 +0200
  Re: xtensa build failures in -next due to DMA API changes Christoph Hellwig <hch@lst.de> - 2015-08-25 22:20 +0200
    Re: xtensa build failures in -next due to DMA API changes Christoph Hellwig <hch@lst.de> - 2015-08-25 22:30 +0200
      Re: xtensa build failures in -next due to DMA API changes Max Filippov <jcmvbkbc@gmail.com> - 2015-08-26 10:00 +0200
        Re: xtensa build failures in -next due to DMA API changes Andrew Morton <akpm@linux-foundation.org> - 2015-08-26 10:00 +0200
          Re: xtensa build failures in -next due to DMA API changes Chris Zankel <chris@zankel.net> - 2015-08-26 20:00 +0200
        Re: xtensa build failures in -next due to DMA API changes Christoph Hellwig <hch@lst.de> - 2015-08-26 19:50 +0200
          Re: xtensa build failures in -next due to DMA API changes Chris Zankel <chris@zankel.net> - 2015-09-01 02:40 +0200
    Re: xtensa build failures in -next due to DMA API changes Andrew Morton <akpm@linux-foundation.org> - 2015-08-25 22:30 +0200
    Re: xtensa build failures in -next due to DMA API changes Guenter Roeck <linux@roeck-us.net> - 2015-08-25 22:30 +0200

csiph-web