From: Raja R Harinath <harinath@cs.umn.edu>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: alsa-devel@alsa-project.org, perex@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: Patch?: linux-2.5.59/sound/soundcore.c referenced non-existant errno variable
Date: Fri, 17 Jan 2003 20:49:36 -0600 [thread overview]
Message-ID: <d9n0lz18an.fsf@bose.cs.umn.edu> (raw)
In-Reply-To: <20030117155717.A6250@baldur.yggdrasil.com> ("Adam J. Richter"'s message of "Fri, 17 Jan 2003 15:57:17 -0800")
Hi,
"Adam J. Richter" <adam@yggdrasil.com> writes:
> linux-2.5.59/sound/sound_firmware.c attempts to use the
> user level system call interface from the kernel, which I understand
> works on i386 and perhaps all architectures, but requires a variable
> named "errno."
Which is provided in-kernel (not for modules) by 'lib/errno.c'.
> (Actually, it mixed things like close() and sys_close(), but that's
> beside the point.)
Those are provided by <linux/unistd.h>, with __KERNEL_SYSCALLS__
defined.
> I could just declare a "static int errno;" in the file,
That was originally there, but removed in 2.5.57 IIRC.
<linux/unistd.h> has 'extern int errno;' -- so 'static int errno;'
would be a bug.
- Hari
--
Raja R Harinath ------------------------------ harinath@cs.umn.edu
next prev parent reply other threads:[~2003-01-18 2:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 23:57 Adam J. Richter
2003-01-18 2:49 ` Raja R Harinath [this message]
2003-01-18 3:13 ` Petr Vandrovec
2003-01-18 15:40 ` Raja R Harinath
2003-01-18 20:27 ` Petr Vandrovec
2003-01-18 20:40 ` Andrew Morton
2003-01-19 4:14 Adam J. Richter
2003-01-20 15:27 ` Horst von Brand
2003-01-21 16:48 ` Bill Davidsen
2003-01-21 17:01 ` Horst von Brand
2003-01-20 19:53 Adam J. Richter
2003-01-21 8:35 ` Horst von Brand
2003-01-20 20:01 Adam J. Richter
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=d9n0lz18an.fsf@bose.cs.umn.edu \
--to=harinath@cs.umn.edu \
--cc=adam@yggdrasil.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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
Powered by JetHome