alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Hans Wennborg <hans@hanshq.net>
To: Joe Perches <joe@perches.com>
Cc: starvik@axis.com, linux-cris-kernel@axis.com,
	linux-kernel@vger.kernel.org,
	kernel-janitors <kernel-janitors@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	devel <devel@driverdev.osuosl.org>,
	linux-cifs@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/1] cris: fix %d confusingly prefixed with 0x in format string
Date: Sat, 02 Aug 2014 18:19:19 -0700	[thread overview]
Message-ID: <53DD8E17.1@hanshq.net> (raw)
In-Reply-To: <1407026806.1835.21.camel@joe-AO725>



On 08/02/2014 05:46 PM, Joe Perches wrote:
> On Sat, 2014-08-02 at 15:20 -0700, Hans Wennborg wrote:
>> Signed-off-by: Hans Wennborg <hans@hanshq.net>
>> ---
>>   arch/cris/arch-v32/drivers/cryptocop.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/cris/arch-v32/drivers/cryptocop.c b/arch/cris/arch-v32/drivers/cryptocop.c
> []
>> @@ -3155,7 +3155,7 @@ static void print_dma_descriptors(struct cryptocop_int_operation *iop)
>>   	printk("print_dma_descriptors start\n");
>>
>>   	printk("iop:\n");
>> -	printk("\tsid: 0x%lld\n", iop->sid);
>> +	printk("\tsid: 0x%llx\n", iop->sid);
>>
>>   	printk("\tcdesc_out: 0x%p\n", iop->cdesc_out);
>>   	printk("\tcdesc_in: 0x%p\n", iop->cdesc_in);
>
> Thanks.
>
> This is a surprisingly common error:
>
> $ /usr/bin/git grep -P '0x\%(?!ull\b|ul\b|u\b|lu\b|llu\b|llux\b|lux\b|lx\b|lluX\b|luX\b|lX\b)[ul]*[ud]'
[...]

Yes, I have a patch for a bunch of these, but I figured it would be 
easier to get it merged if I split it up. (Complete kernel newbie here.)

  - Hans

  reply	other threads:[~2014-08-03  1:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1407018043-648-1-git-send-email-hans@hanshq.net>
     [not found] ` <1407018043-648-1-git-send-email-hans-7z9IcJk4adCsTnJN9+BGXg@public.gmane.org>
2014-08-03  0:46   ` [PATCH 1/1] cris: fix %d confusingly prefixed with 0x in format string Joe Perches
2014-08-03  1:19     ` Hans Wennborg [this message]
2014-08-03  6:10       ` Joe Perches
2014-08-04  0:25         ` Hans Wennborg
2014-08-04  0:33           ` Joe Perches
2014-08-03  2:26     ` Steve French

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=53DD8E17.1@hanshq.net \
    --to=hans@hanshq.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=joe@perches.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-cris-kernel@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=starvik@axis.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;
as well as URLs for NNTP newsgroup(s).