From: Hannes Reinecke <hare@suse.de>
To: Randy Dunlap <rdunlap@infradead.org>,
"James E.J. Bottomley" <JBottomley@parallels.com>,
Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
Dario Ballabio <ballabio_dario@emc.com>
Subject: Re: [PATCH -next] scsi: fix u14-34f printk format warnings
Date: Fri, 01 Aug 2014 11:24:44 +0200 [thread overview]
Message-ID: <53DB5CDC.1060405@suse.de> (raw)
In-Reply-To: <53DA6E25.4090409@infradead.org>
On 07/31/2014 06:26 PM, Randy Dunlap wrote:
> any comments?
>
> Thanks.
>
> On 07/24/14 11:07, Randy Dunlap wrote:
>> From: Randy Dunlap <rdunlap@infradead.org>
>>
>> Fix printk format warnings (seen on i386 builds):
>>
>> ../drivers/scsi/u14-34f.c: In function 'port_detect':
>> ../drivers/scsi/u14-34f.c:630:28: warning: format '%u' expects argument of type 'unsigned int', but argument 4 has type 'u64' [-Wformat=]
>> ../drivers/scsi/u14-34f.c: In function 'u14_34f_queuecommand_lck':
>> ../drivers/scsi/u14-34f.c:1290:25: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 6 has type 'int' [-Wformat=]
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: "James E.J. Bottomley" <JBottomley@parallels.com>
>> Cc: Christoph Hellwig <hch@infradead.org>
>> ---
>> drivers/scsi/u14-34f.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> Index: linux-next-20140724/drivers/scsi/u14-34f.c
>> ===================================================================
>> --- linux-next-20140724.orig/drivers/scsi/u14-34f.c
>> +++ linux-next-20140724/drivers/scsi/u14-34f.c
>> @@ -1006,7 +1006,7 @@ static int port_detect \
>> sh[j]->irq, dma_name, sh[j]->sg_tablesize, sh[j]->can_queue);
>>
>> if (sh[j]->max_id > 8 || sh[j]->max_lun > 8)
>> - printk("%s: wide SCSI support enabled, max_id %u, max_lun %u.\n",
>> + printk("%s: wide SCSI support enabled, max_id %u, max_lun %llu.\n",
>> BN(j), sh[j]->max_id, sh[j]->max_lun);
>>
>> for (i = 0; i <= sh[j]->max_channel; i++)
>> @@ -1285,7 +1285,7 @@ static int u14_34f_queuecommand_lck(stru
>> cpp->cpp_index = i;
>> SCpnt->host_scribble = (unsigned char *) &cpp->cpp_index;
>>
>> - if (do_trace) printk("%s: qcomm, mbox %d, target %d.%d:%llu.\n",
>> + if (do_trace) printk("%s: qcomm, mbox %d, target %d.%d:%u.\n",
>> BN(j), i, SCpnt->device->channel, SCpnt->device->id,
>> (u8)SCpnt->device->lun);
>>
>> --
>
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-08-01 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 18:07 [PATCH -next] scsi: fix u14-34f printk format warnings Randy Dunlap
2014-07-31 16:26 ` Randy Dunlap
2014-07-31 17:29 ` Christoph Hellwig
2014-08-01 9:24 ` Hannes Reinecke [this message]
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=53DB5CDC.1060405@suse.de \
--to=hare@suse.de \
--cc=JBottomley@parallels.com \
--cc=ballabio_dario@emc.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).