Re: [PATCH] bus: mvebu-mbus: use %pad to print phys_addr_t

2016-03-30 Thread Gregory CLEMENT
Hi Arnd, On mar., mars 29 2016, Arnd Bergmann wrote: > On Tuesday 29 March 2016 18:04:47 Gregory CLEMENT wrote: >> >> What is the status of this patch? >> >> Do you plan to send a second version with the title fixed as suggested >> by Joe Perches? >> >> Also do you expect that I collect thi

Re: [PATCH] bus: mvebu-mbus: use %pad to print phys_addr_t

2016-03-29 Thread Arnd Bergmann
On Tuesday 29 March 2016 18:04:47 Gregory CLEMENT wrote: > > What is the status of this patch? > > Do you plan to send a second version with the title fixed as suggested > by Joe Perches? > > Also do you expect that I collect this patch in the mvebu subsystem? Right now, it's on my long-term to

Re: [PATCH] bus: mvebu-mbus: use %pad to print phys_addr_t

2016-03-29 Thread Gregory CLEMENT
Hi Arnd, On mar., mars 15 2016, Arnd Bergmann wrote: > A recent change to the mbus driver added a warning printk that > prints a phys_addr_t using the %x format string, which fails in > case we build with 64-bit phys_addr_t: > > drivers/bus/mvebu-mbus.c: In function 'mvebu_mbus_get_dram_win_in

Re: [PATCH] bus: mvebu-mbus: use %pad to print phys_addr_t

2016-03-15 Thread Joe Perches
On Tue, 2016-03-15 at 11:03 +0100, Arnd Bergmann wrote: > A recent change to the mbus driver added a warning printk that > prints a phys_addr_t using the %x format string, which fails in > case we build with 64-bit phys_addr_t: Hey Arnd. This is a bad patch subject, %pad is for a dma_addr_t. The

[PATCH] bus: mvebu-mbus: use %pad to print phys_addr_t

2016-03-15 Thread Arnd Bergmann
A recent change to the mbus driver added a warning printk that prints a phys_addr_t using the %x format string, which fails in case we build with 64-bit phys_addr_t: drivers/bus/mvebu-mbus.c: In function 'mvebu_mbus_get_dram_win_info': drivers/bus/mvebu-mbus.c:975:9: error: format '%x' expects arg