From: Emil Goode <emilgoode@gmail.com>
To: Joe Perches <joe@perches.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: use the new %pa format specifier for dma_addr_t
Date: Sat, 01 Jun 2013 19:09:26 +0000 [thread overview]
Message-ID: <20130601190926.GA5541@debian> (raw)
In-Reply-To: <1370111350.2098.1.camel@joe-AO722>
I see, will send a second version.
Thank's
Emil
On Sat, Jun 01, 2013 at 11:29:10AM -0700, Joe Perches wrote:
> On Sat, 2013-06-01 at 20:02 +0200, Emil Goode wrote:
> > This patch makes use of the new format specifier %pa that was introduced
> > by the following commit.
> >
> > 7d7992108d02aa92ad4c77e5d9ce14088c942e75
> > ("lib/vsprintf.c: add %pa format specifier for phys_addr_t types")
> []
> > diff --git a/drivers/usb/musb/musb_host.c b/drivers/usb/musb/musb_host.c
> []
> > @@ -1756,12 +1756,11 @@ void musb_host_rx(struct musb *musb, u8 epnum)
> []
> > - dev_dbg(musb->controller, "RX%d count %d, buffer 0x%llx len %d/%d\n",
> > + dev_dbg(musb->controller, "RX%d count %d, buffer 0x%pa len %d/%d\n",
>
> This would emit 0x0x<addr>
>
> When you use %pa, don't add 0x
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Emil Goode <emilgoode@gmail.com>
To: Joe Perches <joe@perches.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: use the new %pa format specifier for dma_addr_t
Date: Sat, 1 Jun 2013 21:09:26 +0200 [thread overview]
Message-ID: <20130601190926.GA5541@debian> (raw)
In-Reply-To: <1370111350.2098.1.camel@joe-AO722>
I see, will send a second version.
Thank's
Emil
On Sat, Jun 01, 2013 at 11:29:10AM -0700, Joe Perches wrote:
> On Sat, 2013-06-01 at 20:02 +0200, Emil Goode wrote:
> > This patch makes use of the new format specifier %pa that was introduced
> > by the following commit.
> >
> > 7d7992108d02aa92ad4c77e5d9ce14088c942e75
> > ("lib/vsprintf.c: add %pa format specifier for phys_addr_t types")
> []
> > diff --git a/drivers/usb/musb/musb_host.c b/drivers/usb/musb/musb_host.c
> []
> > @@ -1756,12 +1756,11 @@ void musb_host_rx(struct musb *musb, u8 epnum)
> []
> > - dev_dbg(musb->controller, "RX%d count %d, buffer 0x%llx len %d/%d\n",
> > + dev_dbg(musb->controller, "RX%d count %d, buffer 0x%pa len %d/%d\n",
>
> This would emit 0x0x<addr>
>
> When you use %pa, don't add 0x
>
>
next prev parent reply other threads:[~2013-06-01 19:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 18:02 [PATCH] usb: musb: use the new %pa format specifier for dma_addr_t Emil Goode
2013-06-01 18:02 ` Emil Goode
2013-06-01 18:29 ` Joe Perches
2013-06-01 18:29 ` Joe Perches
2013-06-01 19:09 ` Emil Goode [this message]
2013-06-01 19:09 ` Emil Goode
2013-06-01 20:31 ` Joe Perches
2013-06-01 20:31 ` Joe Perches
2013-06-01 21:56 ` Randy Dunlap
2013-06-01 21:56 ` Randy Dunlap
2013-06-01 22:16 ` Joe Perches
2013-06-01 22:16 ` Joe Perches
2013-06-01 23:06 ` Emil Goode
2013-06-01 23:06 ` Emil Goode
2013-06-01 23:22 ` Joe Perches
2013-06-01 23:22 ` Joe Perches
2013-06-02 13:32 ` Emil Goode
2013-06-02 13:32 ` Emil Goode
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=20130601190926.GA5541@debian \
--to=emilgoode@gmail.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--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 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.