linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@uga.edu>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: chas@locutus.cmf.nrl.navy.mil, linux-kernel@vger.kernel.org,
	davem@redhat.com
Subject: seq_file and proc_dir_entry data (was Re: [PATCH 5/8] 2.5.74 - seq_file conversion of /proc/net/atm (vc))
Date: Wed, 09 Jul 2003 10:35:51 -0400	[thread overview]
Message-ID: <87brw3epiw.fsf_-_@uga.edu> (raw)
In-Reply-To: <20030709022946.G11897@electric-eye.fr.zoreil.com> (Francois Romieu's message of "Wed, 9 Jul 2003 02:29:46 +0200")

On creating a proc entry, it's possible to set the data field to an
arbitrary pointer value.  Later, that pointer value can be used in
callbacks to do interesting things, like access persistent data
associated with the proc file.

I had to rewrite seq_read so that when it calls the start operation it
passes a pointer to a struct (not an loff_t) with iterator info and
also a pointer to the proc_dir_entry data field.

Would it be possible to modify seq_file to give easier access to the
data field of proc_dir_entry, or is seq_file too general for that to
be practical?

-- 
--Ed L Cashin            |   PGP public key:
  ecashin@uga.edu        |   http://noserose.net/e/pgp/


  reply	other threads:[~2003-07-09 14:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09  0:11 [PATCHKIT] 2.5.74 - seq_file conversion of /proc/net/atm Francois Romieu
2003-07-09  0:23 ` [PATCH 1/8] 2.5.74 - seq_file conversion of /proc/net/atm (devices) Francois Romieu
2003-07-09  0:26 ` [PATCH 2/8] 2.5.74 - seq_file conversion of /proc/net/atm (vc helpers) Francois Romieu
2003-07-09  0:27 ` [PATCH 3/8] 2.5.74 - seq_file conversion of /proc/net/atm (pvc) Francois Romieu
2003-07-09  0:28 ` [PATCH 4/8] 2.5.74 - seq_file conversion of /proc/net/atm (svc) Francois Romieu
2003-07-09  0:29 ` [PATCH 5/8] 2.5.74 - seq_file conversion of /proc/net/atm (vc) Francois Romieu
2003-07-09 14:35   ` Ed L Cashin [this message]
2003-07-09  0:30 ` [PATCH 6/8] 2.5.74 - seq_file conversion of /proc/net/atm (arp) Francois Romieu
2003-07-09  0:31 ` [PATCH 7/8] 2.5.74 - seq_file conversion of /proc/net/atm (lec) Francois Romieu
2003-07-09  0:33 ` [PATCH 8/8] 2.5.74 - seq_file conversion of /proc/net/atm (cleanup) Francois Romieu
2003-07-10  5:49 ` [PATCHKIT] 2.5.74 - seq_file conversion of /proc/net/atm David S. Miller
2003-07-10 10:48   ` chas williams

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=87brw3epiw.fsf_-_@uga.edu \
    --to=ecashin@uga.edu \
    --cc=chas@locutus.cmf.nrl.navy.mil \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romieu@fr.zoreil.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;
as well as URLs for NNTP newsgroup(s).