From: Arjan van de Ven <arjanv@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, hch@infradead.org,
linux-kernel@vger.kernel.org, dcn@sgi.com
Subject: Re: [IA64] allow OEM written modules to make calls to ia64 OEM SAL functions.
Date: Sun, 5 Sep 2004 00:36:42 +0200 [thread overview]
Message-ID: <20040904223642.GA27637@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040904152949.5bf7bca8.akpm@osdl.org>
On Sat, Sep 04, 2004 at 03:29:49PM -0700, Andrew Morton wrote:
> Arjan van de Ven <arjanv@redhat.com> wrote:
> >
> > 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..
>
> Yes. Guys, these are the rules we all live by.
>
> Arjan, please submit a patch.
well all that is needed is to revert changeset
1.1803.128.1 since that is the entire and exclusive purpose of this
changeset.. but for your convenience below
--- b/arch/ia64/kernel/sal.c 2004-09-03 15:07:22 -07:00
+++ a/arch/ia64/kernel/sal.c 2004-09-03 15:07:22 -07:00
@@ -10,7 +10,6 @@
#include <linux/kernel.h>
#include <linux/init.h>
-#include <linux/module.h>
#include <linux/spinlock.h>
#include <linux/string.h>
@@ -263,40 +262,3 @@
p += SAL_DESC_SIZE(*p);
}
}
-
-int
-ia64_sal_oemcall(struct ia64_sal_retval *isrvp, u64 oemfunc, u64 arg1,
- u64 arg2, u64 arg3, u64 arg4, u64 arg5, u64 arg6, u64 arg7)
-{
- if (oemfunc < IA64_SAL_OEMFUNC_MIN || oemfunc > IA64_SAL_OEMFUNC_MAX)
- return -1;
- SAL_CALL(*isrvp, oemfunc, arg1, arg2, arg3, arg4, arg5, arg6, arg7);
- return 0;
-}
-EXPORT_SYMBOL(ia64_sal_oemcall);
-
-int
-ia64_sal_oemcall_nolock(struct ia64_sal_retval *isrvp, u64 oemfunc, u64 arg1,
- u64 arg2, u64 arg3, u64 arg4, u64 arg5, u64 arg6,
- u64 arg7)
-{
- if (oemfunc < IA64_SAL_OEMFUNC_MIN || oemfunc > IA64_SAL_OEMFUNC_MAX)
- return -1;
- SAL_CALL_NOLOCK(*isrvp, oemfunc, arg1, arg2, arg3, arg4, arg5, arg6,
- arg7);
- return 0;
-}
-EXPORT_SYMBOL(ia64_sal_oemcall_nolock);
-
-int
-ia64_sal_oemcall_reentrant(struct ia64_sal_retval *isrvp, u64 oemfunc,
- u64 arg1, u64 arg2, u64 arg3, u64 arg4, u64 arg5,
- u64 arg6, u64 arg7)
-{
- if (oemfunc < IA64_SAL_OEMFUNC_MIN || oemfunc > IA64_SAL_OEMFUNC_MAX)
- return -1;
- SAL_CALL_REENTRANT(*isrvp, oemfunc, arg1, arg2, arg3, arg4, arg5, arg6,
- arg7);
- return 0;
-}
-EXPORT_SYMBOL(ia64_sal_oemcall_reentrant);
reverted:
--- b/include/asm-ia64/sal.h 2004-09-03 15:07:22 -07:00
+++ a/include/asm-ia64/sal.h 2004-09-03 15:07:22 -07:00
@@ -819,16 +819,6 @@
long r8; long r9; long r10; long r11;
};
-#define IA64_SAL_OEMFUNC_MIN 0x02000000
-#define IA64_SAL_OEMFUNC_MAX 0x03ffffff
-
-extern int ia64_sal_oemcall(struct ia64_sal_retval *, u64, u64, u64, u64, u64,
- u64, u64, u64);
-extern int ia64_sal_oemcall_nolock(struct ia64_sal_retval *, u64, u64, u64,
- u64, u64, u64, u64, u64);
-extern int ia64_sal_oemcall_reentrant(struct ia64_sal_retval *, u64, u64, u64,
- u64, u64, u64, u64, u64);
-
#endif /* __ASSEMBLY__ */
#endif /* _ASM_IA64_SAL_H */
next prev parent reply other threads:[~2004-09-04 22:36 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
2004-09-04 22:29 ` Andrew Morton
2004-09-04 22:36 ` Arjan van de Ven [this message]
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=20040904223642.GA27637@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=akpm@osdl.org \
--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