Re: [PATCH] scsi: lpfc: use proper format string for dma_addr_t

2017-02-28 Thread James Smart
Arnd, Thank you. Looks good. -- james Signed-off-by: James Smart On 2/27/2017 12:37 PM, Arnd Bergmann wrote: dma_addr_t may be either u32 or u64, depending on the kernel configuration, and we get a warning for the 32-bit case: drivers/scsi/lpfc/lpfc_nvme.c: In function 'lpfc_nvme_ls_req':

Re: [PATCH] scsi: lpfc: use proper format string for dma_addr_t

2017-02-27 Thread Martin K. Petersen
> "Arnd" == Arnd Bergmann writes: Arnd> dma_addr_t may be either u32 or u64, depending on the kernel Arnd> configuration, and we get a warning for the 32-bit case: Applied to 4.11/scsi-fixes. -- Martin K. Petersen Oracle Linux Engineering

[PATCH] scsi: lpfc: use proper format string for dma_addr_t

2017-02-27 Thread Arnd Bergmann
dma_addr_t may be either u32 or u64, depending on the kernel configuration, and we get a warning for the 32-bit case: drivers/scsi/lpfc/lpfc_nvme.c: In function 'lpfc_nvme_ls_req': drivers/scsi/lpfc/lpfc_logmsg.h:52:52: error: format '%llu' expects argument of type 'long long unsigned int', but a