mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sven Heinicke <sven@research.nj.nec.com>
To: Jorge Nerin <comandante@zaralinux.com>
Cc: Sven Heinicke <sven@research.nj.nec.com>, linux-kernel@vger.kernel.org
Subject: Re: /proc/stat description for proc.txt
Date: Wed, 21 Nov 2001 10:47:27 -0500 (EST)	[thread overview]
Message-ID: <15355.52367.747990.149824@abasin.nj.nec.com> (raw)
In-Reply-To: <3BFAE0FD.8010909@zaralinux.com>
In-Reply-To: <15347.57175.887835.525156@abasin.nj.nec.com> <3BFAE0FD.8010909@zaralinux.com>


Yea, well, I didn't get any message about my proc.txt patch going into
the kernel.  So it's back to the source I guess. :(

    Sven

Jorge Nerin writes:
 > Sven Heinicke wrote:
 > 
 > > I got tired at looking proc_misc.c to see what /proc/stat was
 > > reporting about.  So here is my noted patched into proc.txt about the
 > > /proc/stat file.  It's a patch off the 2.4.15-pre1 proc.txt, but it
 > > worked fine patching it into 2.4.15-pre4 kernel.  Between which I
 > > don't actually think proc.txt has changed.
 > > 
 > > 	   Sven
 > > 
 > > [snip]
 > 
 > >  Summary
 > > -
 > > 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/
 > > 
 > > 
 > 
 > Hey I wrote the last update to this file about exactly one year ago, and 
 > I wrote it for the same reasons as you.
 > 
 > I needed some info about some files and fields in the proc tree, and the 
 > responses was 1) read proc.txt (seriously out of date) and 2) look at 
 > the source Luke.
 > 
 > So I also got tired of seeking & greping around the code and wrote a 
 > small update, nice to see someone updated it again.
 > 
 > P.D. It should be updated by the people who updates the interface, at 
 > least minimally, the name and meaning of the fields or where to look.
 > 
 > -- 
 > Jorge Nerin
 > <comandante@zaralinux.com>
 > 

      parent reply	other threads:[~2001-11-21 15:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15 15:29 Sven Heinicke
2001-11-15 18:59 ` Andreas Dilger
2001-11-16 16:50   ` Anthony DeRobertis
2001-11-15 20:18 ` Sven Heinicke
2001-11-15 20:37   ` Andreas Dilger
2001-11-15 20:43   ` Sven Heinicke
2001-11-15 21:00     ` Andreas Schwab
2001-11-15 21:10     ` Sven Heinicke
2001-11-15 21:51       ` Marius Gedminas
2001-11-20 23:02 ` Jorge Nerin
2001-11-21 15:47 ` Sven Heinicke [this message]

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=15355.52367.747990.149824@abasin.nj.nec.com \
    --to=sven@research.nj.nec.com \
    --cc=comandante@zaralinux.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®