From: Arjan van de Ven <arjanv@redhat.com>
To: torvalds@osdl.org, Christoph Hellwig <hch@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dcn@sgi.com
Subject: Re: [IA64] allow OEM written modules to make calls to ia64 OEM SAL functions.
Date: Sat, 4 Sep 2004 11:37:45 +0200 [thread overview]
Message-ID: <20040904093745.GB5313@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040904103529.C13149@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On Sat, Sep 04, 2004 at 10:35:29AM +0100, Christoph Hellwig wrote:
> On Sat, Sep 04, 2004 at 08:51:47AM +0200, Arjan van de Ven wrote:
> > On Wed, 2004-08-25 at 20:27, Linux Kernel Mailing List wrote:
> > > ChangeSet 1.1803.128.1, 2004/08/25 18:27:33+00:00, dcn@sgi.com
> > >
> > > [IA64] allow OEM written modules to make calls to ia64 OEM SAL functions.
> > >
> > > Add wrapper functions for SAL_CALL(), SAL_CALL_NOLOCK(), and
> > > SAL_CALL_REENTRANT() that allow OEM written modules to make
> > > calls to ia64 OEM SAL functions.
> > >
> >
> > are there any such modules? Are they GPL licensed or all proprietary ?
>
> SGI has stated they have propritary modules that need this, that's why it's
> got added despite my objections.
if there are no open source modules that use these exports I would like to
ask these exports to be undone again..
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-04 9:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200409032207.i83M7CKj015068@hera.kernel.org>
2004-09-04 6:51 ` [IA64] allow OEM written modules to make calls to ia64 OEM SAL functions Arjan van de Ven
2004-09-04 9:35 ` Christoph Hellwig
2004-09-04 9:37 ` Arjan van de Ven [this message]
2004-09-04 22:29 ` Andrew Morton
2004-09-04 22:36 ` Arjan van de Ven
2004-09-07 16:28 ` Robin Holt
2004-09-04 16:43 ` Alan Cox
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=20040904093745.GB5313@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=dcn@sgi.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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