From: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
alsa-devel@alsa-project.org, Sam Ravnborg <sam@ravnborg.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: usr/include/linux/soundcard.h warnings for 'make headers_check'
Date: Sat, 24 Jan 2009 12:20:03 +0530 [thread overview]
Message-ID: <3f9a31f40901232250i27a673a9r8b0620f968e351e1@mail.gmail.com> (raw)
In-Reply-To: <s5h7i4psepm.wl%tiwai@suse.de>
On Wed, Jan 21, 2009 at 5:38 AM, Takashi Iwai <tiwai@suse.de> wrote:
> At Tue, 20 Jan 2009 21:08:22 +0530,
> Jaswinder Singh Rajput wrote:
>>
>> usr/include/linux/soundcard.h is giving following warnings for 'make headers_check':
>> usr/include/linux/soundcard.h:1047: extern's make no sense in userspace
>> usr/include/linux/soundcard.h:1048: extern's make no sense in userspace
>> usr/include/linux/soundcard.h:1049: extern's make no sense in userspace
>> usr/include/linux/soundcard.h:1050: extern's make no sense in userspace
>> usr/include/linux/soundcard.h:1051: extern's make no sense in userspace
>> usr/include/linux/soundcard.h:1053: extern's make no sense in userspace
>> usr/include/linux/soundcard.h:1055: extern's make no sense in userspace
>> usr/include/linux/soundcard.h:1056: extern's make no sense in userspace
>> usr/include/linux/soundcard.h:1061: extern's make no sense in userspace
>> usr/include/linux/soundcard.h:1062: extern's make no sense in userspace
>> usr/include/linux/soundcard.h:1078: extern's make no sense in userspace
>> usr/include/linux/soundcard.h:1079: extern's make no sense in userspace
>>
>> Do we need to fix these warnings.
>
> No, these are declarations for OSS-lib.
> It doesn't belong to kernel, but it's better to keep it for
> compatibility in some way.
>
Do you find some better place for:
void seqbuf_dump(void); /* This function must be provided by programs */
extern int OSS_init(int seqfd, int buflen);
extern void OSS_seqbuf_dump(int fd, unsigned char *buf, int buflen);
extern void OSS_seq_advbuf(int len, int fd, unsigned char *buf, int buflen);
extern void OSS_seq_needbuf(int len, int fd, unsigned char *buf, int buflen);
extern void OSS_patch_caching(int dev, int chn, int patch,
int fd, unsigned char *buf, int buflen);
extern void OSS_drum_caching(int dev, int chn, int patch,
int fd, unsigned char *buf, int buflen);
extern void OSS_write_patch(int fd, unsigned char *buf, int len);
extern int OSS_write_patch2(int fd, unsigned char *buf, int len);
..
#ifdef OSSLIB
# define SEQ_USE_EXTBUF() \
extern unsigned char *_seqbuf; \
extern int _seqbuflen;extern int _seqbufptr
# define SEQ_DEFINEBUF(len) SEQ_USE_EXTBUF();static int
_requested_seqbuflen=len
# define _SEQ_ADVBUF(len) OSS_seq_advbuf(len, seqfd, _seqbuf, _seqbuflen)
# define _SEQ_NEEDBUF(len) OSS_seq_needbuf(len, seqfd, _seqbuf, _seqbuflen)
# define SEQ_DUMPBUF() OSS_seqbuf_dump(seqfd, _seqbuf, _seqbuflen)
# define SEQ_LOAD_GMINSTR(dev, instr) \
OSS_patch_caching(dev, -1, instr, seqfd, _seqbuf, _seqbuflen)
# define SEQ_LOAD_GMDRUM(dev, drum) \
OSS_drum_caching(dev, -1, drum, seqfd, _seqbuf, _seqbuflen)
#else /* !OSSLIB */
# define SEQ_LOAD_GMINSTR(dev, instr)
# define SEQ_LOAD_GMDRUM(dev, drum)
# define SEQ_USE_EXTBUF() \
extern unsigned char _seqbuf[]; \
extern int _seqbuflen;extern int _seqbufptr
..
what are your plans.
--
JSR
prev parent reply other threads:[~2009-01-24 6:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 15:38 Jaswinder Singh Rajput
2009-01-21 0:08 ` Takashi Iwai
2009-01-21 0:25 ` Jaswinder Singh Rajput
2009-01-21 5:41 ` Sam Ravnborg
2009-02-03 20:27 ` Arnd Bergmann
2009-02-04 4:04 ` Jaswinder Singh Rajput
2009-02-04 6:39 ` Takashi Iwai
2009-02-04 8:34 ` Jaswinder Singh Rajput
2009-02-04 9:03 ` Takashi Iwai
2009-02-04 10:37 ` Jaswinder Singh Rajput
2009-02-04 10:52 ` Takashi Iwai
2009-02-04 11:31 ` Jaswinder Singh Rajput
2009-02-04 11:43 ` Takashi Iwai
2009-02-04 12:51 ` Arnd Bergmann
2009-02-04 12:58 ` Takashi Iwai
2009-02-04 13:44 ` Jaswinder Singh Rajput
2009-02-04 13:49 ` Takashi Iwai
2009-02-04 14:02 ` Arnd Bergmann
2009-02-09 23:06 ` Takashi Iwai
2009-01-24 6:50 ` Jaswinder Singh Rajput [this message]
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=3f9a31f40901232250i27a673a9r8b0620f968e351e1@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®