All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, Al Viro <viro@ZenIV.linux.org.uk>
Subject: include/sound/soc-dai.h: "codec" declared twice
Date: Tue, 28 Apr 2009 15:33:27 -0400	[thread overview]
Message-ID: <49F75A07.6090001@garzik.org> (raw)

Compiling with LLVM's clang yielded this:

> include/sound/soc-dai.h:224:25: error: member of anonymous union redeclares 'codec'
>                 struct snd_soc_codec *codec;
>                                       ^
> include/sound/soc-dai.h:214:24: note: previous declaration is here
>         struct snd_soc_codec *codec;
>                               ^
> 2 diagnostics generated.

And indeed, we see

struct snd_soc_dai {
[...]
         /* DAI runtime info */
         struct snd_pcm_runtime *runtime;
         struct snd_soc_codec *codec;

[...]
         /* parent codec/platform */
         union {
                 struct snd_soc_codec *codec;
                 struct snd_soc_platform *platform;
         };

         struct list_head list;
};


                 reply	other threads:[~2009-04-28 19:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=49F75A07.6090001@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    --cc=viro@ZenIV.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 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.