From: Jonathan Corbet <corbet@lwn.net>
To: randy.dunlap@verizon.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] seq_file_howto
Date: Tue, 25 Feb 2003 13:34:44 -0700 [thread overview]
Message-ID: <20030225203444.30004.qmail@eklektix.com> (raw)
> acme prodded me into doing this a few weeks (or months?) ago.
> It still needs some additional info for using single_open()
> and single_release(), but I'd like to get some comments on it
> and then add it to linux/Documentation/filesystems/ or post it
> on the web somewhere, like kernelnewbies.org.
Gee...I did one too, including a simple sample module which shows how it
all works; see http://lwn.net/Articles/22355/. It's part of the larger
"driver porting" series at http://lwn.net/Articles/driver-porting/; there's
a dozen articles there now, most of which have passed out of the
subscription period and are freely available.
jon
Jonathan Corbet
Executive editor, LWN.net
corbet@lwn.net
next reply other threads:[~2003-02-25 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 20:34 Jonathan Corbet [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-23 4:03 [RFC] seq_file_howto Randy.Dunlap
2003-02-23 4:43 ` Randy.Dunlap
2003-02-23 10:10 ` Andries Brouwer
2003-02-24 0:48 ` Randy.Dunlap
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=20030225203444.30004.qmail@eklektix.com \
--to=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@verizon.net \
/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