From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jon Masters <jcm@jonmasters.org>
Cc: mingo@elte.hu, tglx@linutronix.de, williams@redhat.com,
jcm@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PULL] hardware latency detector
Date: Thu, 18 Jun 2009 18:25:51 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906181824540.16802@localhost.localdomain> (raw)
In-Reply-To: <E1MHSnC-0006bC-OW@tonnant>
On Thu, 18 Jun 2009, Jon Masters wrote:
>
> Please pull "hwlat", the hardware latency detector for 2.6.31.
I really want to know more before I pull. Has this been in -next?
Discussed on lkml? How does it work? What does it do?
Thanks,
Linus
next prev parent reply other threads:[~2009-06-19 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 1:21 [PULL] hardware latency detector Jon Masters
2009-06-19 1:25 ` Linus Torvalds [this message]
2009-06-19 1:32 ` Jon Masters
-- strict thread matches above, loose matches on Subject: below --
2009-06-19 1:16 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=alpine.LFD.2.01.0906181824540.16802@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=jcm@jonmasters.org \
--cc=jcm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox