From: Kevin Hilman <khilman@linaro.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: linus.walleij@linaro.org, vinod.koul@intel.com,
linux-kernel@vger.kernel.org,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH] dma: ste_dma: Fix warning when CONFIG_ARM_LPAE=y
Date: Thu, 22 Aug 2013 05:37:52 -0700 [thread overview]
Message-ID: <87mwo9x5nj.fsf@linaro.org> (raw)
In-Reply-To: <1377131642-19494-1-git-send-email-festevam@gmail.com> (Fabio Estevam's message of "Wed, 21 Aug 2013 21:34:02 -0300")
Fabio Estevam <festevam@gmail.com> writes:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> When CONFIG_ARM_LPAE=y the following build warning are generated:
>
> drivers/dma/ste_dma40.c:3228:2: warning: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'resource_size_t' [-Wformat]
> drivers/dma/ste_dma40.c:3582:3: warning: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'resource_size_t' [-Wformat]
> drivers/dma/ste_dma40.c:3582:3: warning: format '%x' expects argument of type 'unsigned int', but argument 5 has type 'resource_size_t' [-Wformat]
> drivers/dma/ste_dma40.c:3593:5: warning: format '%x' expects argument of type 'unsigned int', but argument 5 has type 'resource_size_t' [-Wformat]
>
> According to Documentation/printk-formats.txt '%pa' can be used to properly
> print 'resource_size_t'.
>
> Also, for printing memory region the '%pr' is more convenient.
>
> Reported-by: Kevin Hilman <khilman@linaro.org>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Acked-by: Kevin Hilman <khilman@linaro.org>
And I verified the compile problem is gone away with arm_v7_defconfig +
CONFIG_ARM_LPAE=y
Thanks for the fix!
Kevin
next prev parent reply other threads:[~2013-08-22 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 0:34 [PATCH] dma: ste_dma: Fix warning when CONFIG_ARM_LPAE=y Fabio Estevam
2013-08-22 12:37 ` Kevin Hilman [this message]
2013-08-23 18:03 ` Linus Walleij
2013-08-25 10:47 ` Vinod Koul
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=87mwo9x5nj.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.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