From: Chen Gong <gong.chen@linux.intel.com>
To: Luming Yu <luming.yu@gmail.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
Jon Masters <jonathan@jonmasters.org>,
Jon Masters <jcm@redhat.com>
Subject: Re: [PATCH update 0/3] HW-latency: hardware latency test 0.10
Date: Sun, 11 Nov 2012 03:23:04 -0500 [thread overview]
Message-ID: <20121111082304.GA27037@gchen.bj.intel.com> (raw)
In-Reply-To: <1352602102-2390-1-git-send-email-luming.yu@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1808 bytes --]
On Sat, Nov 10, 2012 at 09:48:19PM -0500, Luming Yu wrote:
> Date: Sat, 10 Nov 2012 21:48:19 -0500
> From: Luming Yu <luming.yu@gmail.com>
> To: arnd@arndb.de, linux-kernel@vger.kernel.org
> Cc: Luming Yu <luming.yu@gmail.com>, Jon Masters <jonathan@jonmasters.org>,
> Jon Masters <jcm@redhat.com>
> Subject: [PATCH update 0/3] HW-latency: hardware latency test 0.10
> X-Mailer: git-send-email 1.7.12.1
>
> Update the previous patch series to ACK all comments I've recevied so far
> for the tool: e.g. 1.Acked Jon Masters in source code as many code are from
> jcm, thanks very much Jon. 2. squashed all changes against new file I added into
> one. 3. Make it useful on non-x86.
>
> Please review and commit to misc tree. I will update the patch series if anyone
> has anymore comments.
>
> Thanks very much!!!
>
> Luming Yu (3):
> HW-latency: hardware latency test 0.10
> x86: Delete too many "Fast TSC .." in dmesg from HW_latency cyclic
> sampling
> fs: Fix crash caused by write to dummy debugfs interface like
> HW_latency exposed
>
> arch/x86/kernel/tsc.c | 2 +-
> drivers/misc/Kconfig | 6 +
> drivers/misc/Makefile | 1 +
> drivers/misc/hw_latency_test.c | 939 +++++++++++++++++++++++++++++++++++++++++
> fs/libfs.c | 2 +-
> 5 files changed, 948 insertions(+), 2 deletions(-)
> create mode 100644 drivers/misc/hw_latency_test.c
>
> --
> 1.7.12.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Hi, Luming
Would you please send the first patch to LKML, too?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-11 8:29 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 ` Chen Gong [this message]
2012-11-12 4:13 ` [PATCH update 0/3] HW-latency: hardware latency test 0.10 Jon Masters
2012-11-18 9:30 ` Luming Yu
2012-11-19 7:30 ` Jon Masters
2012-11-27 2:43 ` Luming Yu
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=20121111082304.GA27037@gchen.bj.intel.com \
--to=gong.chen@linux.intel.com \
--cc=arnd@arndb.de \
--cc=jcm@redhat.com \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.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 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).