From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Alexander Viro <viro@math.psu.edu>,
lkml <linux-kernel@vger.kernel.org>,
Jeff Muizelaar <kernel@infidigm.net>
Subject: [PATCH] add seq file helpers from 2.5 (fwd)
Date: Thu, 10 Jul 2003 00:02:05 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.55L.0307100000100.6316@freak.distro.conectiva> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 454 bytes --]
Viro,
I think you are the right person to review that.
Would you do me the favour?
---------- Forwarded message ----------
Date: Wed, 09 Jul 2003 20:16:54 -0400
From: Jeff Muizelaar <kernel@infidigm.net>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: [PATCH] add seq file helpers from 2.5
Marcelo,
The attached patch adds the single_* helpers that have been in 2.5 since
May 2002, it also adds some missing includes that are in 2.5.
-Jeff
[-- Attachment #2: Type: TEXT/PLAIN, Size: 2001 bytes --]
diff -urN linux-2.4.21-bk1/fs/seq_file.c linux-2.4.21-bk1-seq-file-single/fs/seq_file.c
--- linux-2.4.21-bk1/fs/seq_file.c 2003-06-13 10:51:37.000000000 -0400
+++ linux-2.4.21-bk1-seq-file-single/fs/seq_file.c 2003-07-09 20:06:25.000000000 -0400
@@ -295,3 +295,45 @@
m->count = m->size;
return -1;
}
+
+static void *single_start(struct seq_file *p, loff_t *pos)
+{
+ return NULL + (*pos == 0);
+}
+
+static void *single_next(struct seq_file *p, void *v, loff_t *pos)
+{
+ ++*pos;
+ return NULL;
+}
+
+static void single_stop(struct seq_file *p, void *v)
+{
+}
+
+int single_open(struct file *file, int (*show)(struct seq_file *, void*), void *data)
+{
+ struct seq_operations *op = kmalloc(sizeof(*op), GFP_KERNEL);
+ int res = -ENOMEM;
+
+ if (op) {
+ op->start = single_start;
+ op->next = single_next;
+ op->stop = single_stop;
+ op->show = show;
+ res = seq_open(file, op);
+ if (!res)
+ ((struct seq_file *)file->private_data)->private = data;
+ else
+ kfree(op);
+ }
+ return res;
+}
+
+int single_release(struct inode *inode, struct file *file)
+{
+ struct seq_operations *op = ((struct seq_file *)file->private_data)->op;
+ int res = seq_release(inode, file);
+ kfree(op);
+ return res;
+}
diff -urN linux-2.4.21-bk1/include/linux/seq_file.h linux-2.4.21-bk1-seq-file-single/include/linux/seq_file.h
--- linux-2.4.21-bk1/include/linux/seq_file.h 2002-08-02 20:39:45.000000000 -0400
+++ linux-2.4.21-bk1-seq-file-single/include/linux/seq_file.h 2003-07-06 08:57:25.000000000 -0400
@@ -2,7 +2,13 @@
#define _LINUX_SEQ_FILE_H
#ifdef __KERNEL__
+#include <linux/types.h>
+#include <linux/string.h>
+#include <asm/semaphore.h>
+
struct seq_operations;
+struct file;
+struct inode;
struct seq_file {
char *buf;
@@ -52,5 +58,8 @@
int seq_printf(struct seq_file *, const char *, ...)
__attribute__ ((format (printf,2,3)));
+
+int single_open(struct file *, int (*)(struct seq_file *, void *), void *);
+int single_release(struct inode *, struct file *);
#endif
#endif
next reply other threads:[~2003-07-10 2:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 3:02 Marcelo Tosatti [this message]
2003-07-10 5:04 ` [PATCH] add seq file helpers from 2.5 (fwd) Randy.Dunlap
2003-07-10 18:28 ` Chris Wright
2003-07-10 18:45 ` Chris Wright
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=Pine.LNX.4.55L.0307100000100.6316@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=kernel@infidigm.net \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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).