From: Andrew Morton <akpm@zip.com.au>
To: Alexander Viro <viro@math.psu.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Bernhard Rosenkraenzer <bero@redhat.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] exporting seq_* stuff
Date: Sat, 29 Dec 2001 12:32:53 -0800 [thread overview]
Message-ID: <3C2E2875.8E2EF36D@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.42.0112291626430.23274-200000@bochum.stuttgart.redhat.com> <Pine.GSO.4.21.0112291328160.5671-100000@weyl.math.psu.edu>
Alexander Viro wrote:
>
> [snip the attached horror]
[ replace with a different one :-) ]
> diff -urN C2-pre3/kernel/ksyms.c C2-pre3-fix/kernel/ksyms.c
> --- C2-pre3/kernel/ksyms.c Thu Dec 27 19:48:04 2001
> +++ C2-pre3-fix/kernel/ksyms.c Sat Dec 29 13:48:12 2001
> @@ -46,6 +46,7 @@
> #include <linux/tty.h>
> #include <linux/in6.h>
> #include <linux/completion.h>
> +#include <linux/seq_file.h>
> #include <asm/checksum.h>
>
> #if defined(CONFIG_PROC_FS)
> @@ -480,6 +481,12 @@
> EXPORT_SYMBOL(reparent_to_init);
> EXPORT_SYMBOL(daemonize);
> EXPORT_SYMBOL(csum_partial); /* for networking and md */
> +EXPORT_SYMBOL(seq_escape);
> +EXPORT_SYMBOL(seq_printf);
> +EXPORT_SYMBOL(seq_open);
> +EXPORT_SYMBOL(seq_release);
> +EXPORT_SYMBOL(seq_read);
> +EXPORT_SYMBOL(seq_lseek);
Personally, I prefer to see the EXPORT_SYMBOL() near the
definition of the thing being exported. For functions, the
convention I like is:
void foo()
{
}
EXPORT_SYMBOL(foo);
It's nicer, and prevents patch conflicts.
I'd propose that we drop the concept of EXPORT_OBJ by making all
files eligible for exporting symbols, and that the janitors be given
a mandate to scrap the ksyms files.
Is this acceptable?
-
next prev parent reply other threads:[~2001-12-29 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-29 15:55 [PATCH] Workaround for NFS breakage in 2.5.2pre3 Bernhard Rosenkraenzer
2001-12-29 18:52 ` [PATCH] exporting seq_* stuff Alexander Viro
2001-12-29 20:32 ` Andrew Morton [this message]
2001-12-29 20:40 ` Linus Torvalds
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=3C2E2875.8E2EF36D@zip.com.au \
--to=akpm@zip.com.au \
--cc=bero@redhat.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--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