From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: linux-rt-users@vger.kernel.org, Luotao Fu <lfu@pengutronix.de>
Subject: Re: appearance of /proc/interrupts ?
Date: Thu, 11 Jan 2007 16:19:34 +0100 [thread overview]
Message-ID: <45A65586.3080506@imc-berlin.de> (raw)
In-Reply-To: <20070111115025.GF29495@pengutronix.de>
Robert Schwebel wrote:
> On Thu, Jan 11, 2007 at 12:04:17PM +0100, Steven Scholz wrote:
>> Ah. I see. Thanks! Maybe someone could update the wiki then! ;-)
>
> Yep; Fu, could you please update the HOWTO?
And is it possible that the "command line" mentioned for the "Interval 500
micro seconds" test cases is wrong? "-i 10000" is 10ms, right?
--
Steven
next prev parent reply other threads:[~2007-01-11 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 9:51 appearance of /proc/interrupts ? Steven Scholz
2007-01-11 9:50 ` Ingo Molnar
2007-01-11 11:04 ` Steven Scholz
2007-01-11 11:50 ` Robert Schwebel
2007-01-11 15:19 ` Steven Scholz [this message]
2007-01-12 9:13 ` Luotao Fu
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=45A65586.3080506@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=lfu@pengutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=r.schwebel@pengutronix.de \
/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).