From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] CMA: Fix the phys_addr_t print types
Date: Sat, 23 Nov 2013 22:44:21 -0500 [thread overview]
Message-ID: <52917615.6000504@ti.com> (raw)
In-Reply-To: <20131124034345.GA3873@kroah.com>
On Saturday 23 November 2013 10:43 PM, Greg Kroah-Hartman wrote:
> On Sat, Nov 23, 2013 at 10:37:01PM -0500, Santosh Shilimkar wrote:
>> Otherwise prints would truncate the variables on LPAE machines.
>>
>> Cc: Marek Szyprowski <m.szyprowski@samsung.com>
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> ---
>> drivers/base/dma-contiguous.c | 9 ++++-----
>> 1 file changed, 4 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/base/dma-contiguous.c b/drivers/base/dma-contiguous.c
>> index 165c2c2..b303a98 100644
>> --- a/drivers/base/dma-contiguous.c
>> +++ b/drivers/base/dma-contiguous.c
>> @@ -201,9 +201,8 @@ int __init dma_contiguous_reserve_area(phys_addr_t size, phys_addr_t base,
>> phys_addr_t alignment;
>> int ret = 0;
>>
>> - pr_debug("%s(size %lx, base %08lx, limit %08lx)\n", __func__,
>> - (unsigned long)size, (unsigned long)base,
>> - (unsigned long)limit);
>> + pr_info("%s(size %pa, base %pa, limit %pa)\n", __func__,
>> + &size, &base, &limit);
>
> Why did you change the logging level of this message?
>
Opps... That was accidental. Will post updated version.
regards,
Santosh
next prev parent reply other threads:[~2013-11-24 3:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-24 3:37 [PATCH] CMA: Fix the phys_addr_t print types Santosh Shilimkar
2013-11-24 3:43 ` Greg Kroah-Hartman
2013-11-24 3:44 ` Santosh Shilimkar [this message]
2013-11-24 3:44 ` Greg Kroah-Hartman
2013-11-24 3:45 ` Santosh Shilimkar
2013-11-24 4:10 ` Greg Kroah-Hartman
2013-11-24 4:28 ` Santosh Shilimkar
2013-11-25 10:46 ` Marek Szyprowski
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=52917615.6000504@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).