Re: [PATCH] vme: fake: fix build for 64-bit dma_addr_t

2016-09-08 Thread Martyn Welch
On Tue, Sep 06, 2016 at 02:59:41PM +0200, Arnd Bergmann wrote: > casting between dma_addr_t and a pointer is generally tricky, > as they might not be the same size and almost never point into > the same address space. With 32-bit ARM systems and LPAE, we > get this warning for the vme_fake driver

Re: [PATCH] vme: fake: fix build for 64-bit dma_addr_t

2016-09-06 Thread Arnd Bergmann
On Tuesday, September 6, 2016 10:39:25 PM CEST Dan Carpenter wrote: > On Tue, Sep 06, 2016 at 02:59:41PM +0200, Arnd Bergmann wrote: > > casting between dma_addr_t and a pointer is generally tricky, > > as they might not be the same size and almost never point into > > the same address space. With

Re: [PATCH] vme: fake: fix build for 64-bit dma_addr_t

2016-09-06 Thread Dan Carpenter
On Tue, Sep 06, 2016 at 02:59:41PM +0200, Arnd Bergmann wrote: > casting between dma_addr_t and a pointer is generally tricky, > as they might not be the same size and almost never point into > the same address space. With 32-bit ARM systems and LPAE, we > get this warning for the vme_fake driver

[PATCH] vme: fake: fix build for 64-bit dma_addr_t

2016-09-06 Thread Arnd Bergmann
casting between dma_addr_t and a pointer is generally tricky, as they might not be the same size and almost never point into the same address space. With 32-bit ARM systems and LPAE, we get this warning for the vme_fake driver that stores a pointer in a dma_addr_t variable: