From: Takashi Iwai <tiwai@suse•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org
Subject: Re: linux-next: tree build failure
Date: Fri, 28 Nov 2008 11:25:22 +0100 [thread overview]
Message-ID: <s5hljv4406l.wl%tiwai@suse.de> (raw)
In-Reply-To: <20081128210412.a7df2494.sfr@canb.auug.org.au>
At Fri, 28 Nov 2008 21:04:12 +1100,
Stephen Rothwell wrote:
>
> Hi Takashi,
>
> Today's linux-next build (i386 defconfig) failed like this:
>
> sound/pci/hda/hda_intel.c: In function 'azx_codec_create':
> sound/pci/hda/hda_intel.c:1236: error: 'power_save' undeclared (first use in this function)
>
> Caused by commit fee2fba3586f78762ecc5f432dfd3602765a31b3 ("ALSA: hda -
> Move power_save option to hda_intel.c").
>
> I have reverted that commit. It needs to be fixed soon.
It was already fixed on sound.git tree in this morning.
Pull again if possible.
thanks,
Takashi
next prev parent reply other threads:[~2008-11-28 10:25 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 10:04 linux-next: tree build failure Stephen Rothwell
2008-11-28 10:25 ` Takashi Iwai [this message]
2008-11-28 10:43 ` Stephen Rothwell
2008-11-28 17:23 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2009-12-16 7:21 Stephen Rothwell
2009-12-16 9:02 ` Felipe Balbi
2009-12-16 10:10 ` Liam Girdwood
2009-10-01 3:19 Stephen Rothwell
2009-10-01 7:58 ` Jens Axboe
2009-10-01 10:41 ` Stephen Rothwell
2009-09-29 9:28 Jan Beulich
[not found] ` <4AC1E15502000078000516B5-Qfbpwmsw6RoS3W1tAdPHOtBPR1lH4CV8@public.gmane.org>
2009-09-29 9:51 ` roel kluin
[not found] ` <25e057c00909290251h55c0dc25o4ab1f2e84c920dca-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-30 6:29 ` Jan Beulich
2009-09-29 23:39 ` Hollis Blanchard
[not found] ` <1254267572.15622.1621.camel-yDUrRDS8jBVhsM67afOH+sxtgHpCUUYS@public.gmane.org>
2009-09-30 6:35 ` Jan Beulich
[not found] ` <4AC318450200007800017355-Qfbpwmsw6RoS3W1tAdPHOtBPR1lH4CV8@public.gmane.org>
2009-10-02 15:48 ` Hollis Blanchard
2009-10-05 6:58 ` Jan Beulich
2009-10-09 19:14 ` Hollis Blanchard
2009-10-14 22:57 ` Hollis Blanchard
2009-10-15 7:27 ` Jan Beulich
2009-10-19 18:19 ` Hollis Blanchard
2009-10-20 1:12 ` Rusty Russell
[not found] ` <200910201142.34006.rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
2009-10-20 1:29 ` Hollis Blanchard
2009-09-24 5:21 Stephen Rothwell
[not found] ` <20090924152102.8d7d40cf.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-09-29 0:00 ` Hollis Blanchard
2009-08-17 8:39 Stephen Rothwell
2009-08-03 0:35 Stephen Rothwell
2009-08-03 1:01 ` NeilBrown
2009-08-03 1:30 ` Stephen Rothwell
2009-07-27 7:53 Stephen Rothwell
2009-07-27 9:21 ` Karsten Keil
2009-07-27 15:06 ` David Miller
2009-07-28 4:22 ` Stephen Rothwell
2009-04-07 3:41 Stephen Rothwell
2009-04-07 10:00 ` Mark Brown
2009-04-08 1:48 ` Takashi Iwai
2009-03-23 9:38 Stephen Rothwell
2009-03-23 22:27 ` Mauro Carvalho Chehab
2009-03-23 23:25 ` Stephen Rothwell
2009-03-05 7:41 Stephen Rothwell
2009-03-06 5:01 ` Rusty Russell
2009-01-16 5:37 Stephen Rothwell
2009-01-16 7:25 ` Peter Zijlstra
2009-01-16 9:03 ` Ingo Molnar
2009-01-16 10:39 ` Stephen Rothwell
2009-01-16 10:53 ` Ingo Molnar
2009-01-16 11:53 ` Stephen Rothwell
2009-01-16 12:32 ` Ingo Molnar
2008-10-21 8:30 Stephen Rothwell
2008-08-25 10:33 Stephen Rothwell
2008-08-25 16:36 ` Steven Rostedt
2008-06-30 14:35 Stephen Rothwell
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=s5hljv4406l.wl%tiwai@suse.de \
--to=tiwai@suse$(echo .)de \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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