public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mitchel Humpherys <mitchelh@codeaurora.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@linuxdriverproject.org,
	Android Kernel Team <kernel-team@android.com>,
	Colin Cross <ccross@android.com>,
	John Stultz <john.stultz@linaro.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: ion: chunk_heap: use %pa for printing dma_addr_t's
Date: Thu, 09 Apr 2015 16:19:13 -0700	[thread overview]
Message-ID: <vnkw3848j3f2.fsf@mitchelh-linux1.qualcomm.com> (raw)
In-Reply-To: <20150409223839.GA24054@kroah.com> (Greg Kroah-Hartman's message of "Fri, 10 Apr 2015 00:38:39 +0200")

On Thu, Apr 09 2015 at 03:38:39 PM, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> On Thu, Apr 09, 2015 at 03:31:14PM -0700, Mitchel Humpherys wrote:
>> We're currently using %lu and %ld to print some variables of type
>> dma_addr_t, which results in the following warning when dma_addr_t is
>> 64-bits wide:
>> 
>>     drivers/staging/android/ion/ion_chunk_heap.c: In function 'ion_chunk_heap_create':
>>     drivers/staging/android/ion/ion_chunk_heap.c:176:2: warning: format '%lu' expects argument of type 'long unsigned int', but argument 3 has type 'dma_addr_t' [-Wformat=]
>>       pr_info("%s: base %lu size %zu align %ld\n", __func__, chunk_heap->base,
>>       ^
>>     drivers/staging/android/ion/ion_chunk_heap.c:176:2: warning: format '%ld' expects argument of type 'long int', but argument 5 has type 'dma_addr_t' [-Wformat=]
>> 
>> Fix this by using %pa as instructed in printk-formats.txt.
>> 
>> Signed-off-by: Mitchel Humpherys <mitchelh@codeaurora.org>
>> ---
>>  drivers/staging/android/ion/ion_chunk_heap.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>> 
>> diff --git a/drivers/staging/android/ion/ion_chunk_heap.c b/drivers/staging/android/ion/ion_chunk_heap.c
>> index 3e6ec2ee6802..f0b7c8e68422 100644
>> --- a/drivers/staging/android/ion/ion_chunk_heap.c
>> +++ b/drivers/staging/android/ion/ion_chunk_heap.c
>> @@ -173,8 +173,8 @@ struct ion_heap *ion_chunk_heap_create(struct ion_platform_heap *heap_data)
>>  	chunk_heap->heap.ops = &chunk_heap_ops;
>>  	chunk_heap->heap.type = ION_HEAP_TYPE_CHUNK;
>>  	chunk_heap->heap.flags = ION_HEAP_FLAG_DEFER_FREE;
>> -	pr_info("%s: base %lu size %zu align %ld\n", __func__, chunk_heap->base,
>> -		heap_data->size, heap_data->align);
>> +	pr_info("%s: base %pa size %zu align %pa\n", __func__,
>> +		&chunk_heap->base, heap_data->size, &heap_data->align);
>
> Shouldn't this be a debug message, and not printed out for everyone to
> see all the time?

Yeah that'd probably be better.  I'll send a patch.


-Mitch

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2015-04-09 23:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 22:31 [PATCH] staging: ion: chunk_heap: use %pa for printing dma_addr_t's Mitchel Humpherys
2015-04-09 22:38 ` Greg Kroah-Hartman
2015-04-09 23:19   ` Mitchel Humpherys [this message]
2015-04-09 22:48 ` Colin Cross
2015-04-09 23:20   ` Mitchel Humpherys

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=vnkw3848j3f2.fsf@mitchelh-linux1.qualcomm.com \
    --to=mitchelh@codeaurora.org \
    --cc=ccross@android.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.stultz@linaro.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox