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: build warning after merge of the sound tree
Date: Tue, 30 Mar 2010 14:48:09 +1100 [thread overview]
Message-ID: <20100330144809.77620889.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
Hi Takashi,
After merging the sound tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
sound/pci/hda/patch_realtek.c: In function 'fillup_priv_adc_nids':
sound/pci/hda/patch_realtek.c:5120: warning: format '%s' expects type 'char *', but argument 2 has type 'int'
sound/pci/hda/patch_realtek.c:5120: warning: too few arguments for format
Introduced by commit 6694635d3ae1b038d7a0e38b80637db867c7c8e2 ("ALSA: hda
- Fix ADC/MUX assignment of ALC269 codec").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-03-30 3:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 3:48 Stephen Rothwell [this message]
2010-03-30 6:07 ` linux-next: build warning after merge of the sound tree Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2025-07-15 7:04 Stephen Rothwell
2024-09-02 3:29 Stephen Rothwell
2024-09-02 6:22 ` Takashi Iwai
2024-09-02 6:49 ` Stephen Rothwell
2024-09-02 6:54 ` Stephen Rothwell
2023-08-25 5:29 Stephen Rothwell
2023-08-25 9:24 ` Takashi Iwai
2023-02-08 23:48 Stephen Rothwell
2023-02-09 3:14 ` Stephen Rothwell
2021-08-23 10:00 Stephen Rothwell
2021-08-23 14:27 ` Takashi Iwai
2020-05-01 4:03 Stephen Rothwell
2020-05-01 7:33 ` Takashi Iwai
2019-12-12 0:28 Stephen Rothwell
2019-01-21 0:21 Stephen Rothwell
2019-01-21 8:13 ` Takashi Iwai
2010-02-23 5:07 Stephen Rothwell
2010-02-23 5:20 ` Luke Yelavich
2010-02-23 7:11 ` Takashi Iwai
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=20100330144809.77620889.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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