From: Clark Williams <williams@redhat.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: frank.rowand@am.sony.com,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
jkacur@redhat.com
Subject: Re: [PATCH v2] rt-tests: printf format compile warning
Date: Thu, 3 May 2012 16:26:33 -0500 [thread overview]
Message-ID: <20120503162633.788367b0@redhat.com> (raw)
In-Reply-To: <4FA2F514.5070104@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
On Thu, 03 May 2012 14:13:56 -0700
Darren Hart <dvhart@linux.intel.com> wrote:
>
>
> On 05/03/2012 12:48 PM, Frank Rowand wrote:
> >
> > V2: use type casting instead of ugly constant in format string
> >
> >
> > Fix printf format string to fix compile warning for ARM 32 bit target.
> >
>
> Oh much better. :-)
>
> > Signed-off-by: Frank Rowand <frank.rowand@am.sony.com>
> > ---
> > src/cyclictest/cyclictest.c | 2 1 + 1 - 0 !
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Index: b/src/cyclictest/cyclictest.c
> > ===================================================================
> > --- a/src/cyclictest/cyclictest.c
> > +++ b/src/cyclictest/cyclictest.c
> > @@ -1575,7 +1575,7 @@ int main(int argc, char **argv)
> > print_tids(parameters, num_threads);
> > if (break_thread_id) {
> > printf("# Break thread: %d\n", break_thread_id);
> > - printf("# Break value: %lu\n", break_thread_value);
> > + printf("# Break value: %llu\n", (unsigned long long)break_thread_value);
> > }
> > }
> >
> >
>
>
Yes, I like this better. I pulled the original and applied this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-05-03 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 19:48 [PATCH v2] rt-tests: printf format compile warning Frank Rowand
2012-05-03 21:13 ` Darren Hart
2012-05-03 21:26 ` Clark Williams [this message]
2012-05-03 22:37 ` John Kacur
2012-05-03 22:41 ` John Kacur
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=20120503162633.788367b0@redhat.com \
--to=williams@redhat.com \
--cc=dvhart@linux.intel.com \
--cc=frank.rowand@am.sony.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).