From: Chris Friesen <cfriesen@nortel.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
Arjan van de Ven <arjan@infradead.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: question on symbol exports
Date: Mon, 07 Feb 2005 17:02:46 -0600 [thread overview]
Message-ID: <4207F396.7080408@nortel.com> (raw)
In-Reply-To: <1107812101.7734.42.camel@gaston>
Benjamin Herrenschmidt wrote:
> Interesting... more than no swap, you must also make sure you have no
> r/w mmap'ed file (which are technically equivalent to swap).
Ah...thanks for the warning.
We want to eventually make it work with swap as well, but that's
substantially more complicated.
> I'm not too fan about exporting those symbols, but I'll talk to paulus,
> it should be possible at least to EXPORT_SYMBOL_GPL them...
I understand the reluctance. I'm perfectly willing to export it GPL in
my private branch as long as you guys don't consider it evil--the module
is going to be GPL anyways.
The alternative would be for me to build my code directly in to the
kernel...just makes it harder for me to debug.
Chris
WARNING: multiple messages have this Message-ID (diff)
From: Chris Friesen <cfriesen@nortel.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: question on symbol exports
Date: Mon, 07 Feb 2005 17:02:46 -0600 [thread overview]
Message-ID: <4207F396.7080408@nortel.com> (raw)
In-Reply-To: <1107812101.7734.42.camel@gaston>
Benjamin Herrenschmidt wrote:
> Interesting... more than no swap, you must also make sure you have no
> r/w mmap'ed file (which are technically equivalent to swap).
Ah...thanks for the warning.
We want to eventually make it work with swap as well, but that's
substantially more complicated.
> I'm not too fan about exporting those symbols, but I'll talk to paulus,
> it should be possible at least to EXPORT_SYMBOL_GPL them...
I understand the reluctance. I'm perfectly willing to export it GPL in
my private branch as long as you guys don't consider it evil--the module
is going to be GPL anyways.
The alternative would be for me to build my code directly in to the
kernel...just makes it harder for me to debug.
Chris
next prev parent reply other threads:[~2005-02-07 23:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 0:15 question on symbol exports Chris Friesen
2005-02-01 7:36 ` Arjan van de Ven
2005-02-01 15:37 ` Chris Friesen
2005-02-01 15:50 ` Arjan van de Ven
2005-02-01 17:00 ` Chris Friesen
[not found] ` <20050204203050.GA5889@dmt.cnet>
2005-02-04 20:14 ` Chris Friesen
2005-02-04 20:14 ` Chris Friesen
2005-02-05 9:19 ` Benjamin Herrenschmidt
2005-02-05 9:19 ` Benjamin Herrenschmidt
2005-02-07 14:44 ` Chris Friesen
2005-02-07 14:44 ` Chris Friesen
2005-02-07 21:35 ` Benjamin Herrenschmidt
2005-02-07 21:35 ` Benjamin Herrenschmidt
2005-02-07 23:02 ` Chris Friesen [this message]
2005-02-07 23:02 ` Chris Friesen
2005-02-07 23:42 ` Dan Malek
2005-02-07 23:42 ` Dan Malek
2005-02-08 15:36 ` Chris Friesen
2005-02-08 15:36 ` Chris Friesen
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=4207F396.7080408@nortel.com \
--to=cfriesen@nortel.com \
--cc=arjan@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.