From: Frank Rowand <frank.rowand@am.sony.com>
To: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"williams@redhat.com" <williams@redhat.com>,
"jkacur@redhat.com" <jkacur@redhat.com>
Cc: "dvhart@linux.intel.com" <dvhart@linux.intel.com>,
"lclaudio@uudg.org" <lclaudio@uudg.org>
Subject: Re: [PATCH 2/2] V3: cyclictest: report large measured clock latency
Date: Tue, 15 May 2012 16:44:37 -0700 [thread overview]
Message-ID: <4FB2EA65.7010101@am.sony.com> (raw)
In-Reply-To: <4FB2E94E.6080008@am.sony.com>
On 05/15/12 16:39, Frank Rowand wrote:
>
> V3: Use src/lib/error.c functions instead of fprintf.
> Fix printf format warnings for 32 bit vs 64 bit systems with cast.
One issue with using warn() and info() instead of fprintf() is that
the compiler no longer warns about format mismatches. Just an FYI...
> Fix bad continuation line white space prefix.
> Remove unused variable zero_diff.
>
< snip >
next prev parent reply other threads:[~2012-05-15 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 23:36 [PATCH 1/2] V3: cyclictest: clean up getopt_long() parameters Frank Rowand
2012-05-15 23:39 ` [PATCH 2/2] V3: cyclictest: report large measured clock latency Frank Rowand
2012-05-15 23:44 ` Frank Rowand [this message]
[not found] <502965C1.2090409@am.sony.com>
2012-10-15 23:43 ` John Kacur
2012-10-16 0:18 ` Frank Rowand
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=4FB2EA65.7010101@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=dvhart@linux.intel.com \
--cc=jkacur@redhat.com \
--cc=lclaudio@uudg.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.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.