From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Takashi Iwai <tiwai@suse•de>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: sound tree build warning
Date: Wed, 8 Jul 2009 14:18:25 +1000 [thread overview]
Message-ID: <20090708141825.da103bc8.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
Hi Takashi,
Today's linux-next build (x86_64 allmodconfig) produced these warnings:
sound/pci/hda/patch_via.c: In function 'via_mux_enum_put':
sound/pci/hda/patch_via.c:395: warning: unused variable 'vendor_id'
sound/pci/hda/patch_via.c: In function 'get_mux_nids':
sound/pci/hda/patch_via.c:1337: warning: unused variable 'type'
sound/pci/hda/patch_via.c:1354: warning: no return statement in function returning non-void
Introduced by commit 337b9d02b4873ceac91565272545fb6fd446d939 ("ALSA: hda
- Fix capture source selection in patch_via.c").
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-07-08 4:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 4:18 Stephen Rothwell [this message]
2009-07-08 5:57 ` [PATCH] sound: pci/hda/patch_via.c fix compilation warning Jaswinder Singh Rajput
2009-07-08 6:00 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2009-07-15 3:13 linux-next: sound tree build warning Stephen Rothwell
2009-07-15 8:35 ` Mark Brown
2009-07-15 9:09 ` Takashi Iwai
2009-07-15 9:12 ` Mark Brown
2009-08-10 4:15 Stephen Rothwell
2009-08-10 7:34 ` Takashi Iwai
2009-08-10 18:43 ` Mark Brown
2009-08-11 3:22 Stephen Rothwell
2009-08-11 6:17 ` Takashi Iwai
2009-08-11 6:21 ` Stephen Rothwell
2009-08-12 1:13 Stephen Rothwell
2009-08-12 5:58 ` Takashi Iwai
2009-08-12 13:33 ` Mark Brown
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=20090708141825.da103bc8.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tiwai@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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