From: John Stebbins <john@stebbins.name>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sys_close undefined on x86_64
Date: Sun, 13 Jun 2004 13:42:26 -0700 [thread overview]
Message-ID: <1087159346.2961.5.camel@Homer> (raw)
In-Reply-To: <20040613002814.GC29873@kroah.com>
Thanks for the pointer. I hadn't heard about the firmware download
subsystem. I just had a look. Seems to be just the thing needed here.
There are other people actively working on this module, so maybe I can
get it done by just suggesting it to them :->
John
On Sat, 2004-06-12 at 17:28, Greg KH wrote:
> On Sat, Jun 12, 2004 at 05:11:18PM -0700, John Stebbins wrote:
> >
> > insmod fails with sys_close undefined message when attempting to load
> > the module.
>
> Why would a kernel module want to call sys_close directly? If it's for
> firmware loading, the module needs to be ported to use the firmware
> download subsystem.
>
> Good luck,
>
> greg k-h
next prev parent reply other threads:[~2004-06-13 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-13 0:11 sys_close undefined on x86_64 John Stebbins
2004-06-13 0:28 ` Greg KH
2004-06-13 20:42 ` John Stebbins [this message]
[not found] <26qTc-8ok-3@gated-at.bofh.it>
2004-06-13 0:38 ` Andi Kleen
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=1087159346.2961.5.camel@Homer \
--to=john@stebbins.name \
--cc=greg@kroah.com \
--cc=linux-kernel@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