From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: calling oem sal functions
Date: Thu, 19 Aug 2004 17:29:04 +0000 [thread overview]
Message-ID: <20040819182904.A11376@infradead.org> (raw)
In-Reply-To: <4124E222.2080105@intel.com>
On Thu, Aug 19, 2004 at 05:23:46PM +0000, Tony Luck wrote:
> Dean,
>
> I've been thinking about this, and it does seem unresonable that there
> is no way for an OEM written module to make a call to an OEM SAL function.
>
> Would something like the (compiles, but untested) attached patch work
> for you? The return value of 0/-1 just indicates whether the SAL call
> was attempted. Callers should look at the status field of the isrvp
> structure to determine the actual success of the call.
>
> Would you also need "_nolock" and "_reentrant" versions?
Please make the exports _GPL so we have the callers under rcontrol.
next prev parent reply other threads:[~2004-08-19 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 17:23 calling oem sal functions Tony Luck
2004-08-19 17:29 ` Christoph Hellwig [this message]
2004-08-19 18:18 ` Robin Holt
2004-08-19 18:21 ` Christoph Hellwig
2004-08-19 18:29 ` Dean Nelson
2004-08-19 18:48 ` Jack Steiner
2004-08-19 19:48 ` Robin Holt
2004-08-19 22:14 ` John Lee
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=20040819182904.A11376@infradead.org \
--to=hch@infradead.org \
--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