public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Korty <joe.korty@ccur.com>
Cc: Sven-Thorsten Dietrich <sdietrich@novell.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	mingo@elte.hu, tglx@linutronix.de,
	linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	jason.baietto@ccur.com
Subject: Re: [PATCH] expand /proc/interrupts to include missing vectors, v2
Date: Mon, 30 Jul 2007 18:48:36 -0700	[thread overview]
Message-ID: <20070730184836.63ad64d2.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070731001718.GA14295@tsunami.ccur.com>

On Mon, 30 Jul 2007 20:17:18 -0400 Joe Korty <joe.korty@ccur.com> wrote:

> +		seq_printf(p, "RES: ");
> +		seq_printf(p, "CAL: ");
> +		seq_printf(p, "TLB: ");
> +		seq_printf(p, "TRM: ");

Documentation/filesystems/proc.txt presently describes NMI:, LOC: and ERR:.
Are you thinking what I'm thinking?  ;)


  parent reply	other threads:[~2007-07-31  1:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 18:05 [PATCH] create /proc/all-interrupts Joe Korty
2007-07-26 18:56 ` H. Peter Anvin
2007-07-30 17:33   ` Sven-Thorsten Dietrich
2007-07-30 19:32     ` Andrew Morton
2007-07-30 19:42       ` Joe Korty
2007-07-31  0:17       ` [PATCH] expand /proc/interrupts to include missing vectors, v2 Joe Korty
2007-07-31  0:48         ` Gabriel C
2007-07-31  1:48         ` Andrew Morton [this message]
2007-07-31 14:19         ` [PATCH] expand /proc/interrupts to include missing vectors, v3 Joe Korty
2007-07-31 17:02           ` Andi Kleen
2007-07-31 20:29             ` Joe Korty
2007-07-31 21:06           ` [PATCH] expand /proc/interrupts to include missing vectors, v4 Joe Korty
2007-08-01 13:29         ` [PATCH] expand /proc/interrupts to include missing vectors, v2 Lennart Sorensen

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=20070730184836.63ad64d2.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=jason.baietto@ccur.com \
    --cc=joe.korty@ccur.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sdietrich@novell.com \
    --cc=tglx@linutronix.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