public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Alsa Devel list <alsa-devel@lists.sourceforge.net>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: [Alsa-devel] 2.6.6-rc2 build warnings
Date: Tue, 24 Aug 2004 14:25:57 +0200	[thread overview]
Message-ID: <s5hwtzog1t6.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040824122116.A5031@flint.arm.linux.org.uk>

At Tue, 24 Aug 2004 12:21:16 +0100,
Russell King wrote:
> 
> A reminder that this problem remains unresolved.

This should have been fixed on linux-sound bk tree, waiting for
pulling.


Takashi

> ----- Forwarded message from Russell King <rmk+alsa@arm.linux.org.uk> -----
> From: Russell King <rmk+alsa@arm.linux.org.uk>
> To: Alsa Devel list <alsa-devel@lists.sourceforge.net>
> Subject: [Alsa-devel] 2.6.6-rc2 build warnings
> Date: Sun, 30 May 2004 11:00:08 +0100
> 
> Someone may wish to look into the cause of this... CONFIG_PCI is
> unselected in this case.
> 
>   CC [M]  sound/core/oss/mixer_oss.o
> In file included from sound/core/oss/mixer_oss.c:26:
> include/sound/core.h:215: warning: `struct pci_dev' declared inside parameter list
> include/sound/core.h:215: warning: its scope is only this definition or declaration, which is probably not what you want
> include/sound/core.h:216: warning: `struct pci_dev' declared inside parameter list
>   CC [M]  sound/core/oss/pcm_oss.o
> In file included from sound/core/oss/pcm_oss.c:35:
> include/sound/core.h:215: warning: `struct pci_dev' declared inside parameter list
> include/sound/core.h:215: warning: its scope is only this definition or declaration, which is probably not what you want
> include/sound/core.h:216: warning: `struct pci_dev' declared inside parameter list
> ...
> 
> -- 
> Russell King
>  Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
>  maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
>                  2.6 Serial core
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g. 
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 
> ----- End forwarded message -----
> 
> -- 
> Russell King
>  Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
>  maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
>                  2.6 Serial core
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

      reply	other threads:[~2004-08-24 12:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 11:21 Fwd: [Alsa-devel] 2.6.6-rc2 build warnings Russell King
2004-08-24 12:25 ` Takashi Iwai [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=s5hwtzog1t6.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    /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