From: Hans Wennborg <hans@hanshq.net>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/15] cpufreq: fix decimal printf format specifiers prefixed with 0x
Date: Wed, 06 Aug 2014 22:53:38 -0700 [thread overview]
Message-ID: <53E31462.2060800@hanshq.net> (raw)
In-Reply-To: <1494298.av10nJMuYA@vostro.rjw.lan>
On 08/06/2014 01:35 PM, Rafael J. Wysocki wrote:
> On Tuesday, August 05, 2014 09:41:48 PM Hans Wennborg wrote:
>> The prefix suggests the number should be printed in hex, so use
>> the %x specifier to do that.
>>
>> Found by using regex suggested by Joe Perches.
>>
>> Signed-off-by: Hans Wennborg <hans@hanshq.net>
>
> This triggers a build warning related to the formats. Care to fix up?
Sure. Sending a new patch, hopefully attached to the same thread (still
working on my git send-mail skills).
- Hans
prev parent reply other threads:[~2014-08-07 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 4:41 [PATCH 02/15] cpufreq: fix decimal printf format specifiers prefixed with 0x Hans Wennborg
2014-08-06 20:35 ` Rafael J. Wysocki
2014-08-07 5:52 ` [PATCH 1/1] cpufreq: fix decimal printf " Hans Wennborg
2014-08-07 5:53 ` Hans Wennborg [this message]
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=53E31462.2060800@hanshq.net \
--to=hans@hanshq.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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