From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: James Smart <james.smart@avagotech.com>,
Dick Kennedy <dick.kennedy@avagotech.com>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Hannes Reinecke <hare@suse.com>,
James Bottomley <JBottomley@Odin.com>,
Sebastian Herbszt <herbszt@gmx.de>,
Johannes Thumshirn <jthumshirn@suse.de>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lpfc: use %zd format string for size_t
Date: Mon, 17 Oct 2016 13:59:08 -0400 [thread overview]
Message-ID: <yq1wph6hn6b.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20161017123605.2217411-1-arnd@arndb.de> (Arnd Bergmann's message of "Mon, 17 Oct 2016 14:35:46 +0200")
>>>>> "Arnd" == Arnd Bergmann <arnd@arndb.de> writes:
Arnd> A recent bugfix introduced a harmless warning in the lpfc driver:
Arnd> drivers/scsi/lpfc/lpfc_init.c: In function 'lpfc_write_firmware':
Arnd> drivers/scsi/lpfc/lpfc_logmsg.h:56:45: error: format '%ld' expects
Arnd> argument of type 'long int', but argument 9 has type 'size_t {aka
Arnd> const unsigned int}' [-Werror=format=]
Arnd> 'size_t' is always the same width as 'long' in the kernel, but the
Arnd> compiler doesn't know that. The %z modifier is what the standard
Arnd> expects to be used here, and this shuts up the warning.
Applied to 4.10/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2016-10-17 17:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 12:35 [PATCH] lpfc: use %zd format string for size_t Arnd Bergmann
2016-10-17 13:39 ` Johannes Thumshirn
2016-10-17 15:53 ` James Smart
2016-10-17 17:59 ` Martin K. Petersen [this message]
2016-10-28 21:03 ` Vineet Gupta
2016-10-28 21:03 ` Vineet Gupta
2016-10-28 21:33 ` Arnd Bergmann
2016-10-28 21:33 ` Arnd Bergmann
2016-10-28 21:44 ` Vineet Gupta
2016-10-28 21:44 ` Vineet Gupta
2016-10-28 21:48 ` Arnd Bergmann
2016-10-28 21:48 ` Arnd Bergmann
2016-10-28 21:52 ` Vineet Gupta
2016-10-28 21:52 ` Vineet Gupta
2016-10-28 21:58 ` Vineet Gupta
2016-10-28 21:58 ` Vineet Gupta
2016-10-28 22:03 ` Arnd Bergmann
2016-10-28 22:03 ` Arnd Bergmann
2016-10-28 23:16 ` Vineet Gupta
2016-10-28 23:16 ` Vineet Gupta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yq1wph6hn6b.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=JBottomley@Odin.com \
--cc=arnd@arndb.de \
--cc=dick.kennedy@avagotech.com \
--cc=hare@suse.com \
--cc=herbszt@gmx.de \
--cc=james.smart@avagotech.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.