From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: [PATCH] 2.6.0-test4 SEQ_START_TOKEN Add #define to seq_file.h (1/6)
Date: Fri, 05 Sep 2003 18:46:49 -0700 [thread overview]
Message-ID: <1062812809.16845.163.camel@localhost.localdomain> (raw)
Code that includes seq_file.h use a magic pointer "(void*)1"
to start a header seq_printf.
These patches convert the magic pointer use to a #define
diff -urN linux-2.6.0-test4/include/linux/seq_file.h SEQ_START_TOKEN/include/linux/seq_file.h
-- linux-2.6.0-test4/include/linux/seq_file.h 2003-08-22 17:02:49.000000000 -0700
+++ SEQ_START_TOKEN/include/linux/seq_file.h 2003-09-04 17:28:19.000000000 -0700
@@ -65,5 +65,8 @@
int single_open(struct file *, int (*)(struct seq_file *, void *), void *);
int single_release(struct inode *, struct file *);
int seq_release_private(struct inode *, struct file *);
+
+#define SEQ_START_TOKEN ((void *)1)
+
#endif
#endif
reply other threads:[~2003-09-06 1:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1062812809.16845.163.camel@localhost.localdomain \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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).