From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "kartilak@cisco.com" <kartilak@cisco.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"nicolas.iooss_linux@m4x.org" <nicolas.iooss_linux@m4x.org>,
"satishkh@cisco.com" <satishkh@cisco.com>,
"sebaddel@cisco.com" <sebaddel@cisco.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] scsi: fnic: add a space after %p in printf format
Date: Mon, 11 Dec 2017 22:22:55 +0000 [thread overview]
Message-ID: <1513030969.2747.19.camel@wdc.com> (raw)
In-Reply-To: <20171210192311.5334-1-nicolas.iooss_linux@m4x.org>
On Sun, 2017-12-10 at 20:23 +0100, Nicolas Iooss wrote:
> fnic_fcpio_icmnd_cmpl_handler() displays the value of sc with:
>
> FNIC_SCSI_DBG(KERN_INFO...
> "... sc = 0x%p"
> "scsi_status ..."
> ...
>
> As the literal strings get merged, the function uses %ps instead of the
> intended raw %p format. Fix this by inserting a space.
>
> Signed-off-by: Nicolas Iooss <nicolas.iooss_linux@m4x.org>
> ---
> drivers/scsi/fnic/fnic_scsi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/fnic/fnic_scsi.c b/drivers/scsi/fnic/fnic_scsi.c
> index 242e2ee494a1..8cbd3c9f0b4c 100644
> --- a/drivers/scsi/fnic/fnic_scsi.c
> +++ b/drivers/scsi/fnic/fnic_scsi.c
> @@ -906,7 +906,7 @@ static void fnic_fcpio_icmnd_cmpl_handler(struct fnic *fnic,
>
> FNIC_SCSI_DBG(KERN_INFO, fnic->lport->host,
> "icmnd_cmpl abts pending "
> - "hdr status = %s tag = 0x%x sc = 0x%p"
> + "hdr status = %s tag = 0x%x sc = 0x%p "
> "scsi_status = %x residual = %d\n",
Since the %p format specifier already inserts a 0x prefix, shouldn't 0x%p be changed
into %p?
Bart.
next prev parent reply other threads:[~2017-12-11 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 19:23 [PATCH 1/1] scsi: fnic: add a space after %p in printf format Nicolas Iooss
2017-12-11 22:22 ` Bart Van Assche [this message]
2017-12-11 22:54 ` Nicolas Iooss
2017-12-11 23:34 ` Bart Van Assche
2017-12-12 2:43 ` Martin K. Petersen
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=1513030969.2747.19.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=kartilak@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nicolas.iooss_linux@m4x.org \
--cc=satishkh@cisco.com \
--cc=sebaddel@cisco.com \
/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.