From: yalin wang <yalin.wang2010@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Don Brace <don.brace@pmcs.com>,
open list <linux-kernel@vger.kernel.org>,
iss_storagedev@hp.com, storagedev@pmcs.com,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [TRIVIAL PATCH] block: Correct misuses of 0x%<decimal>
Date: Tue, 4 Aug 2015 10:19:42 +0800 [thread overview]
Message-ID: <EB2039AE-8999-4D0F-9602-CA5ACF3F66BA@gmail.com> (raw)
In-Reply-To: <67B9124A-73E8-4AA1-81E5-18FAC69D3962@gmail.com>
Ping ?
> On Aug 3, 2015, at 16:56, yalin wang <yalin.wang2010@gmail.com> wrote:
>
>
>> On Aug 3, 2015, at 16:03, Joe Perches <joe@perches.com> wrote:
>>
>> On Mon, 2015-08-03 at 15:25 +0800, yalin wang wrote:
>>>> On Aug 3, 2015, at 04:25, Joe Perches <joe@perches.com> wrote:
>>>>
>>>> Correct misuse of 0x%d in logging messages.
>>>>
>> []
>>> why not use like this : dev_dbg(&h->pdev->dev, " Max outstanding
>>> commands = %#x\n” ?
>>> %#x will add 0x prefix automatically .
>>
>> It's generally a consistency thing.
>> A 0 value would be emitted as 0 and not 0x0.
>>
> i try on my ubuntu ,
>
> static int __init throtl_init(void)
> {
> printk("module init test: %#x %p\n", 0, (void *)0x123);
> return 0;
>
> }
>
> module_init(throtl_init);
>
> #uname -a
> Linux ubuntu 3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>
> #dmesg
> [259356.375586] module init test: 0x0 0000000000000123
>
> it seems don’t need 0x%x for 0, just need %#x for all numbers.
> there are lots of use like this, i can change them if needed:
>
> # egrep -r -i '0x%\d*x' . | wc -l
> 11776
>
>
> Thanks
next prev parent reply other threads:[~2015-08-04 2:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 20:25 [TRIVIAL PATCH] block: Correct misuses of 0x%<decimal> Joe Perches
2015-08-03 7:20 ` Johannes Thumshirn
2015-08-03 7:25 ` yalin wang
2015-08-03 7:25 ` yalin wang
2015-08-03 8:03 ` Joe Perches
2015-08-03 8:56 ` yalin wang
2015-08-04 2:19 ` yalin wang [this message]
2015-08-04 2:27 ` Joe Perches
2015-08-04 4:04 ` yalin wang
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=EB2039AE-8999-4D0F-9602-CA5ACF3F66BA@gmail.com \
--to=yalin.wang2010@gmail.com \
--cc=don.brace@pmcs.com \
--cc=iss_storagedev@hp.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=storagedev@pmcs.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 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.