From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] updated salinfo patch
Date: Wed, 12 Dec 2001 00:13:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805686@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805685@msgid-missing>
On Tue, 11 Dec 2001 16:01:36 -0800,
Jesse Barnes <jbarnes@sgi.com> wrote:
>+MODULE_AUTHOR("Jesse Barnes <jbarnes@sgi.com>");
>+MODULE_DESCRIPTION("/proc interface to IA-64 SAL features");
Better add MODULE_LICENSE("GPL");
>+int salinfo_read(char *page, char **start, off_t off, int count, int *eof, void *data);
Is there any reason to expose salinfo_read, AFAICT it can be static.
If you want to expose that function, you need EXPORT_SYMBOL(salinfo_read)
and salinfo.o must be added to export-objs.
next prev parent reply other threads:[~2001-12-12 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 0:01 [Linux-ia64] updated salinfo patch Jesse Barnes
2001-12-12 0:13 ` Keith Owens [this message]
2001-12-12 0:17 ` Jesse Barnes
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=marc-linux-ia64-105590698805686@msgid-missing \
--to=kaos@ocs.com.au \
--cc=linux-ia64@vger.kernel.org \
/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