Arnd Bergmann 825c6abbc3 scsi: lpfc: use proper format string for dma_addr_t
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 argument 11 has type 'dma_addr_t {aka unsigned int}' [-Werror=format=]
drivers/scsi/lpfc/lpfc_logmsg.h:52:52: error: format '%llu' expects argument of type 'long long unsigned int', but argument 12 has type 'dma_addr_t {aka unsigned int}' [-Werror=format=]
drivers/scsi/lpfc/lpfc_nvme.c: In function 'lpfc_nvme_ls_abort':
drivers/scsi/lpfc/lpfc_logmsg.h:52:52: error: format '%llu' expects argument of type 'long long unsigned int', but argument 11 has type 'dma_addr_t {aka unsigned int}' [-Werror=format=]
drivers/scsi/lpfc/lpfc_logmsg.h:52:52: error: format '%llu' expects argument of type 'long long unsigned int', but argument 12 has type 'dma_addr_t {aka unsigned int}' [-Werror=format=]

printk has a special "%pad" format string that passes the dma address by
reference to solve this problem.

Fixes: 01649561a8b4 ("scsi: lpfc: NVME Initiator: bind to nvme_fc api")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
2017-02-27 22:08:40 -05:00
..
2017-02-22 11:44:32 -08:00
2017-02-22 10:30:38 -08:00
2017-02-20 14:23:40 +01:00
2017-02-22 10:46:44 -08:00
2017-02-20 16:42:43 -08:00
2017-02-21 16:58:32 -08:00
2017-02-21 11:51:42 -08:00
2017-02-21 12:04:54 -08:00
2017-02-21 10:57:33 -08:00
2017-02-22 11:44:32 -08:00
2017-02-22 11:15:59 -08:00
2017-01-25 16:11:55 +00:00
2017-02-20 17:23:57 -08:00
2017-01-30 14:39:20 +01:00
2017-02-20 17:55:15 -08:00
2017-02-20 14:22:50 +01:00
2017-02-14 10:20:35 -08:00
2017-02-22 11:15:59 -08:00
2017-02-20 16:42:43 -08:00
2017-02-11 20:59:41 -05:00