From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Emil Goode <emilgoode@gmail.com>
Cc: balbi@ti.com, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] usb: musb: Fix format specifier warning
Date: Sat, 01 Jun 2013 00:27:30 +0400 [thread overview]
Message-ID: <51A907B2.1070400@cogentembedded.com> (raw)
In-Reply-To: <1370031778-25965-1-git-send-email-emilgoode@gmail.com>
Hello.
On 06/01/2013 12:22 AM, Emil Goode wrote:
> This patch fixes a format specifier warning. dma_addr_t can be either
> u32 or u64 so we should cast to the largest type and change the format
> specifier to %llx.
> The addition of urb->transfer_dma and urb->actual_length is also done a
> few lines below. I have moved this code up and pass the variable buf to
> dev_dbg.
>
> Sparse output:
> drivers/usb/musb/musb_host.c:1761:4: warning:
> format ‘%x’ expects argument of type ‘unsigned int’,
> but argument 6 has type ‘dma_addr_t’ [-Wformat]
>
> Signed-off-by: Emil Goode <emilgoode@gmail.com>
> ---
> drivers/usb/musb/musb_host.c | 11 ++++-------
> 1 file changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/usb/musb/musb_host.c b/drivers/usb/musb/musb_host.c
> index 094cf80..d647ccb 100644
> --- a/drivers/usb/musb/musb_host.c
> +++ b/drivers/usb/musb/musb_host.c
[...]
> @@ -1789,11 +1789,8 @@ void musb_host_rx(struct musb *musb, u8 epnum)
> length = rx_count;
> d->status = d_status;
> buf = urb->transfer_dma + d->offset;
> - } else {
> + } else
You should keep {} on the *else* branch since *if* branch has {},
according to Documentation/CodingStyle.
> length = rx_count;
> - buf = urb->transfer_dma +
> - urb->actual_length;
> - }
WBR, Sergei
next prev parent reply other threads:[~2013-05-31 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 20:22 [PATCH] usb: musb: Fix format specifier warning Emil Goode
2013-05-31 20:27 ` Sergei Shtylyov [this message]
2013-05-31 22:34 ` Andy Shevchenko
2013-05-31 22:39 ` Randy Dunlap
2013-06-01 13:15 ` Andy Shevchenko
2013-06-01 17:11 ` Emil Goode
2013-06-01 22:52 ` Andy Shevchenko
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=51A907B2.1070400@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=balbi@ti.com \
--cc=emilgoode@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox