From: Jon Masters <jonathan@jonmasters.org>
To: linux-next@vger.kernel.org
Subject: [Fwd: [PULL] hardware latency detector]
Date: Thu, 18 Jun 2009 21:27:11 -0400 [thread overview]
Message-ID: <1245374831.14766.19.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 218 bytes --]
Stephen,
I've posted this for merge, but plan to continue developing against the
"master" branch of this tree and then push to "for-linus" before
posting. Perhaps you'd like to add either branch to linux-next.
Jon.
[-- Attachment #2: Forwarded message - [PULL] hardware latency detector --]
[-- Type: message/rfc822, Size: 1845 bytes --]
From: Jon Masters <jcm@jonmasters.org>
To: mingo@elte.hu, tglx@linutronix.de, williams@redhat.com, jcm@redhat.com, jcm@jonmasters.org, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: [PULL] hardware latency detector
Date: Thu, 18 Jun 2009 21:21:22 -0400
Message-ID: <E1MHSnC-0006bC-OW@tonnant>
Linus,
Please pull "hwlat", the hardware latency detector for 2.6.31.
Patches can be pulled from:
git://git.kernel.org/pub/scm/linux/kernel/git/jcm/linux-2.6-hwlat.git for-linus
Jon Masters (2):
hwlat_detector: A system hardware latency detector
hwlat_detector: include linux/delay.h in hwlat_detector
Documentation/hwlat_detector.txt | 64 ++
MAINTAINERS | 9 +
drivers/misc/Kconfig | 28 +
drivers/misc/Makefile | 1 +
drivers/misc/hwlat_detector.c | 1208 ++++++++++++++++++++++++++++++++++++++
5 files changed, 1310 insertions(+), 0 deletions(-)
create mode 100644 Documentation/hwlat_detector.txt
create mode 100644 drivers/misc/hwlat_detector.c
next reply other threads:[~2009-06-19 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 1:27 Jon Masters [this message]
2009-06-19 22:31 ` [Fwd: [PULL] hardware latency detector] Stephen Rothwell
2009-06-21 3:41 ` Jon Masters
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=1245374831.14766.19.camel@localhost.localdomain \
--to=jonathan@jonmasters.org \
--cc=linux-next@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