From: Luming Yu <luming.yu@gmail.com>
To: Jon Masters <jcm@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
Jon Masters <jonathan@jonmasters.org>
Subject: Re: [PATCH update 0/3] HW-latency: hardware latency test 0.10
Date: Tue, 27 Nov 2012 10:43:17 +0800 [thread overview]
Message-ID: <CAJRGBZzW74DVjSmRxoa1vJ52LUXWsHPOXvzdywiTXcmHZUBTxg@mail.gmail.com> (raw)
In-Reply-To: <50A9E019.8050802@redhat.com>
On Mon, Nov 19, 2012 at 3:30 PM, Jon Masters <jcm@redhat.com> wrote:
> On 11/18/2012 04:30 AM, Luming Yu wrote:
>
>> I'd be glad to do anything to push this tool into upstream. Please
>> let me know your thoughts. Thanks !!!! /l
>
> I'm also happy to help test. I'll take a look over the TG holiday at
> your latest version.
>
if we can make the tool upstream, probably we can ask more people to test.
But not sure if arand is interested in this work anymore although he
gave the work
detailed review back to July , thanks Arand...
To push the patch upstream, l'd like to ping you again.
But if other maintainers also interested in the feature, I'd be very
glad to work with them.
Hello Peter, would you like to take this tool to upstream?
Regards /l
prev parent reply other threads:[~2012-11-27 2:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 2:48 [PATCH update 0/3] HW-latency: hardware latency test 0.10 Luming Yu
2012-11-11 2:48 ` [PATCH update 1/3] " Luming Yu
2012-11-11 2:48 ` [PATCH update 2/3] x86: Delete too many "Fast TSC .." in dmesg from HW_latency cyclic sampling Luming Yu
2012-11-11 2:48 ` [PATCH update 3/3] fs: Fix crash caused by write to dummy debugfs interface like HW_latency exposed Luming Yu
2012-11-11 8:23 ` [PATCH update 0/3] HW-latency: hardware latency test 0.10 Chen Gong
2012-11-12 4:13 ` Jon Masters
2012-11-18 9:30 ` Luming Yu
2012-11-19 7:30 ` Jon Masters
2012-11-27 2:43 ` Luming Yu [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=CAJRGBZzW74DVjSmRxoa1vJ52LUXWsHPOXvzdywiTXcmHZUBTxg@mail.gmail.com \
--to=luming.yu@gmail.com \
--cc=arnd@arndb.de \
--cc=hpa@zytor.com \
--cc=jcm@redhat.com \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@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).