From: Christoph Hellwig <hch@infradead.org>
To: Oleg Drokin <green@namesys.com>
Cc: linux-kernel@vger.kernel.org, reiserfs-dev@namesys.com,
viro@math.psu.edu
Subject: Re: Need more symbols to be exported out of kernel
Date: Mon, 19 Aug 2002 15:52:26 +0100 [thread overview]
Message-ID: <20020819155226.A26430@infradead.org> (raw)
In-Reply-To: <20020819184208.A11022@namesys.com>; from green@namesys.com on Mon, Aug 19, 2002 at 06:42:08PM +0400
On Mon, Aug 19, 2002 at 06:42:08PM +0400, Oleg Drokin wrote:
> Hello!
>
> I have implemented file_operations->write() function for reiserfs for
> linux kernel v2.4, and it seems I need these symbols to be exported
> out of kernel for a case when reiserfs is built as a module:
> generic_osync_inode
sounds like a good idea.
> remove_suid
trivial inline, either move it to a header or copy & paste.
> block_commit_write
fine with me.
> I need block_commit_write just because generic_commit_write is doing
> some extra stuff I'd better do myself.
> Will the patch to export these symbols be accepted? (should these be
> exported as GPL sysmbols or not?).
IMHO no _GPL, they are not different from other generic filesystem code.
next prev parent reply other threads:[~2002-08-19 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 14:42 Oleg Drokin
2002-08-19 14:52 ` Christoph Hellwig [this message]
2002-08-19 15:27 ` Oleg Drokin
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=20020819155226.A26430@infradead.org \
--to=hch@infradead.org \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.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
all inboxes | Powered by JetHome®