On 09/11/13 21:38, Olof Johansson wrote: > This resolves some warnings seen when building with CONFIG_ARM_LPAE=y, since > dma_addr_t might then be 64-bit: > > drivers/dma/imx-sdma.c:1092:3: warning: format '%x' expects argument of > type 'unsigned int', but argument 6 has type 'dma_addr_t' [-Wformat=] > drivers/dma/imx-sdma.c:1166:3: warning: format '%x' expects argument of > type 'unsigned int', but argument 6 has type 'dma_addr_t' [-Wformat=] > drivers/dma/imx-dma.c:579:3: warning: format '%x' expects argument of type > 'unsigned int', but argument 6 has type 'dma_addr_t' [-Wformat=] > drivers/dma/imx-dma.c:579:3: warning: format '%x' expects argument of type > 'unsigned int', but argument 7 has type 'dma_addr_t' [-Wformat=] > drivers/dma/imx-dma.c:593:4: warning: format '%x' expects argument of type > 'unsigned int', but argument 9 has type 'dma_addr_t' [-Wformat=] > drivers/dma/imx-dma.c:603:4: warning: format '%x' expects argument of type > 'unsigned int', but argument 9 has type 'dma_addr_t' [-Wformat=] > drivers/dma/imx-dma.c:930:2: warning: format '%x' expects argument of type > 'unsigned int', but argument 6 has type 'dma_addr_t' [-Wformat=] > drivers/dma/imx-dma.c:930:2: warning: format '%x' expects argument of type > 'unsigned int', but argument 7 has type 'dma_addr_t' [-Wformat=] > drivers/dma/imx-dma.c:960:2: warning: format '%x' expects argument of type > 'unsigned int', but argument 6 has type 'dma_addr_t' [-Wformat=] > drivers/dma/imx-dma.c:960:2: warning: format '%x' expects argument of type > 'unsigned int', but argument 7 has type 'dma_addr_t' [-Wformat=] > drivers/dma/ipu/ipu_idmac.c:1235:2: warning: format '%x' expects argument > of type 'unsigned int', but argument 5 has type 'dma_addr_t' [-Wformat=]
I've been tempted to make similar patches, but CONFIG_PHYS_ADDR_T_64BIT and CONFIG_ARCH_DMA_ADDR_T_64BIT are independent AFAICT, and %pa is for physical addresses, not necessarily DMA addresses. Am I confused? -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
