From: Simon Horman <horms@verge.net.au>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] dma/sh: fix rcar-dma.c printk format warnings
Date: Mon, 28 Jul 2014 20:31:08 +0900 [thread overview]
Message-ID: <20140728113107.GA7254@verge.net.au> (raw)
In-Reply-To: <127874008.l4YYrnQ0HU@avalon>
[Replying again using an HTML-free mail client]
On Mon, Jul 28, 2014 at 01:20:59PM +0200, Laurent Pinchart wrote:
> On Saturday 26 July 2014 21:19:30 Vinod Koul wrote:
> > On Fri, Jul 25, 2014 at 10:02:39AM -0700, Randy Dunlap wrote:
> > > From: Randy Dunlap <rdunlap@infradead.org>
> > >
> > > Fix printk format warnings by using size_t modifiers ('z'):
> > >
> > > ../drivers/dma/sh/rcar-dmac.c:759:4: warning: format '%u' expects argument
> > > of type 'unsigned int', but argument 9 has type 'size_t' [-Wformat=]
> > > ../drivers/dma/sh/rcar-dmac.c:759:4: warning: format '%u' expects
> > > argument of type 'unsigned int', but argument 10 has type 'size_t'
> > > [-Wformat=]
> >
> > This is not present in dmaengine trees. Simon is this in your tree?
>
> The patch applies to a new driver under development that Simon took in his
> tree. From what he told me he plans to send a pull request soon.
>
> > > Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> > > Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > > Cc: Dan Williams <dan.j.williams@intel.com>
> > > Cc: dmaengine@vger.kernel.org
>
> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>
> Simon, should I submit a new version that incorporates this change, or do you
> want to include it in your pull request directly (possibly squashing it in the
> original commit) ?
Hi Laurent,
sorry for any confusion that I may have caused.
I will see about squashing this change into the original commit.
> > > ---
> > >
> > > drivers/dma/sh/rcar-dmac.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > Index: linux-next-20140725/drivers/dma/sh/rcar-dmac.c
> > > ===================================================================
> > > --- linux-next-20140725.orig/drivers/dma/sh/rcar-dmac.c
> > > +++ linux-next-20140725/drivers/dma/sh/rcar-dmac.c
> > > @@ -757,7 +757,7 @@ rcar_dmac_chan_prep_sg(struct rcar_dmac_
> > > hwdesc->size = size;
> > >
> > > dev_dbg(chan->chan.device->dev,
> > > - "chan%u: hwdesc %p/%p sgl %u@%p, %u/%u %pad -> %pad\n",
> > > + "chan%u: hwdesc %p/%p sgl %u@%p, %zu/%zu %pad -> %pad\n",
> > > chan->index, hwdesc, desc, i, sg, size, len,
> > > &hwdesc->src_addr, &hwdesc->dst_addr);
>
> --
> Regards,
>
> Laurent Pinchart
>
next prev parent reply other threads:[~2014-07-28 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 17:02 [PATCH -next] dma/sh: fix rcar-dma.c printk format warnings Randy Dunlap
2014-07-26 15:49 ` Vinod Koul
2014-07-28 11:20 ` Laurent Pinchart
2014-07-28 11:31 ` Simon Horman [this message]
2014-07-28 12:08 ` Simon Horman
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=20140728113107.GA7254@verge.net.au \
--to=horms@verge.net.au \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=vinod.koul@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox