All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chunfeng Yun <chunfeng.yun@mediatek.com>,
	Felipe Balbi <felipe.balbi@linux.intel.com>
Subject: Re: linux-next: build warnings after merge of the usb tree
Date: Thu, 2 Nov 2017 09:45:41 +0100	[thread overview]
Message-ID: <20171102084541.GA11064@kroah.com> (raw)
In-Reply-To: <20171102151022.033dc8d0@canb.auug.org.au>

On Thu, Nov 02, 2017 at 03:10:22PM +1100, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the usb tree, today's linux-next build (x86_64 allmodconfig)
> produced these warnings:
> 
> In file included from include/linux/printk.h:327:0,
>                  from include/linux/kernel.h:13,
>                  from include/asm-generic/bug.h:15,
>                  from arch/x86/include/asm/bug.h:81,
>                  from include/linux/bug.h:4,
>                  from include/linux/scatterlist.h:6,
>                  from include/linux/dmapool.h:14,
>                  from drivers/usb/mtu3/mtu3_qmu.c:30:
> drivers/usb/mtu3/mtu3_qmu.c: In function 'mtu3_prepare_tx_gpd':
> drivers/usb/mtu3/mtu3_qmu.c:261:25: warning: format '%p' expects argument of type 'void *', but argument 7 has type 'dma_addr_t {aka long long unsigned int}' [-Wformat=]
>   dev_dbg(mep->mtu->dev, "TX-EP%d queue gpd=%p, enq=%p, qdma=%pad\n",
>                          ^
> include/linux/dynamic_debug.h:134:39: note: in definition of macro 'dynamic_dev_dbg'
>    __dynamic_dev_dbg(&descriptor, dev, fmt, \
>                                        ^
> drivers/usb/mtu3/mtu3_qmu.c:261:2: note: in expansion of macro 'dev_dbg'
>   dev_dbg(mep->mtu->dev, "TX-EP%d queue gpd=%p, enq=%p, qdma=%pad\n",
>   ^
> drivers/usb/mtu3/mtu3_qmu.c: In function 'mtu3_prepare_rx_gpd':
> drivers/usb/mtu3/mtu3_qmu.c:300:25: warning: format '%p' expects argument of type 'void *', but argument 7 has type 'dma_addr_t {aka long long unsigned int}' [-Wformat=]
>   dev_dbg(mep->mtu->dev, "RX-EP%d queue gpd=%p, enq=%p, qdma=%pad\n",
>                          ^
> include/linux/dynamic_debug.h:134:39: note: in definition of macro 'dynamic_dev_dbg'
>    __dynamic_dev_dbg(&descriptor, dev, fmt, \
>                                        ^
> drivers/usb/mtu3/mtu3_qmu.c:300:2: note: in expansion of macro 'dev_dbg'
>   dev_dbg(mep->mtu->dev, "RX-EP%d queue gpd=%p, enq=%p, qdma=%pad\n",
>   ^
> 
> Introduced by commit
> 
>   1a46dfea0841 ("usb: mtu3: support 36-bit DMA address")

I think I have a patch that just landed in my tree to fix this one up.
You should see it soon.

thanks,

greg k-h

  reply	other threads:[~2017-11-02  8:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02  4:10 linux-next: build warnings after merge of the usb tree Stephen Rothwell
2017-11-02  8:45 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-03-17  7:57 Stephen Rothwell
2020-03-17 13:45 ` Andrey Konovalov
2020-03-17 13:53   ` Greg KH
2020-01-07  3:30 Stephen Rothwell
2020-01-07  8:06 ` Krzysztof Kozlowski
2020-01-21  6:28   ` Stephen Rothwell
2020-01-21  7:55     ` Krzysztof Kozlowski
2011-04-14  4:18 Stephen Rothwell
2011-04-14  4:51 ` Greg KH

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=20171102084541.GA11064@kroah.com \
    --to=greg@kroah.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=felipe.balbi@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.