From: Michael Buesch <fsdeveloper@yahoo.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 659] New: compile failure in drivers/media/radio/miropcm20-rds.c
Date: Mon, 5 May 2003 20:12:45 +0200 [thread overview]
Message-ID: <200305052012.58214.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <10320000.1052152541@[10.10.2.4]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 05 May 2003 18:35, Martin J. Bligh wrote:
> http://bugme.osdl.org/show_bug.cgi?id=659
>
> Summary: compile failure in drivers/media/radio/miropcm20-rds.c
> Kernel Version: 2.5.68-bk11
> Status: NEW
> Severity: low
> Owner: bugme-janitors@lists.osdl.org
> Submitter: john@larvalstage.com
>
>
> Distribution: Gentoo 1.4rc4
> Hardware Environment: Abit KG7-RAID, AMD AthlonXP 2100+ Palomino
> Software Environment: gcc 3.2.2, glibc 2.3.1, ld 2.13.90.0.18
> Problem Description:
>
> gcc -Wp,-MD,drivers/media/radio/.miropcm20-rds.o.d -D__KERNEL__ -Iinclude
> -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
> -fno-common -pipe -mpreferred-stack-boundary=2 -march=athlon
> -Iinclude/asm-i386/mach-default -nostdinc -iwithprefix include
> -DKBUILD_BASENAME=miropcm20_rds -DKBUILD_MODNAME=miropcm20_rds -c -o
> drivers/media/radio/.tmp_miropcm20-rds.o
> drivers/media/radio/miropcm20-rds.c drivers/media/radio/miropcm20-rds.c:23:
> warning: `struct inode' declared inside parameter list
> drivers/media/radio/miropcm20-rds.c:23: warning: its scope is only this
> definition or declaration, which is probably not what you want
> drivers/media/radio/miropcm20-rds.c:38: warning: `struct inode' declared
> inside parameter list
> drivers/media/radio/miropcm20-rds.c:106: variable `rds_fops' has
> initializer but incomplete type
> drivers/media/radio/miropcm20-rds.c:107: unknown field `owner' specified in
> initializer
> drivers/media/radio/miropcm20-rds.c:107: warning: excess elements in struct
> initializer
> drivers/media/radio/miropcm20-rds.c:107: warning: (near initialization for
> `rds_fops')
> drivers/media/radio/miropcm20-rds.c:108: unknown field `read' specified in
> initializer
> drivers/media/radio/miropcm20-rds.c:108: warning: excess elements in struct
> initializer
> drivers/media/radio/miropcm20-rds.c:108: warning: (near initialization for
> `rds_fops')
> drivers/media/radio/miropcm20-rds.c:109: unknown field `open' specified in
> initializer
> drivers/media/radio/miropcm20-rds.c:109: warning: excess elements in struct
> initializer
> drivers/media/radio/miropcm20-rds.c:109: warning: (near initialization for
> `rds_fops')
> drivers/media/radio/miropcm20-rds.c:110: unknown field `release' specified
> in initializer
> drivers/media/radio/miropcm20-rds.c:111: warning: excess elements in struct
> initializer
> drivers/media/radio/miropcm20-rds.c:111: warning: (near initialization for
> `rds_fops')
> drivers/media/radio/miropcm20-rds.c:106: storage size of `rds_fops' isn't
> known make[3]: *** [drivers/media/radio/miropcm20-rds.o] Error 1
> make[2]: *** [drivers/media/radio] Error 2
> make[1]: *** [drivers/media] Error 2
> make: *** [drivers] Error 2
>
>
> Steps to reproduce:
>
> Multimedia devices --->
> Radio Adapters --->
> <*> miroSOUND PCM20 radio RDS user interface (EXPERIMENTAL)
>
> CONFIG_RADIO_MIROPCM20_RDS=y
>
2.5.69 compiles for me, so it seems to be fixed.
- --
Regards Michael Büsch
http://www.8ung.at/tuxsoft
20:11:33 up 2:36, 3 users, load average: 1.17, 1.63, 1.50
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+tqmqoxoigfggmSgRAlhjAJ913EJa4+VIdcDsKIECATn0yY7GvQCcD2/W
Ffd9jsee2DCn99S0uDTiljc=
=yDHo
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2003-05-05 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 16:35 [Bug 659] New: compile failure in drivers/media/radio/miropcm20-rds.c Martin J. Bligh
2003-05-05 18:12 ` Michael Buesch [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=200305052012.58214.fsdeveloper@yahoo.de \
--to=fsdeveloper@yahoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.