From: Takashi Iwai <tiwai@suse.de>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: tiwai@suse.de, linux-next@vger.kernel.org
Subject: Re: linux-next: "ALSA: hda - Fix build of patch_sigmatel.c" commit breaks sparc
Date: Sun, 18 Mar 2012 21:27:04 +0100 [thread overview]
Message-ID: <s5hfwd5hcyv.wl%tiwai@suse.de> (raw)
In-Reply-To: <CAP=VYLrxdFQfF5bZ1wEc3qbTP8=r+wkdiE-_Tj+rTgYEoUPKKA@mail.gmail.com>
At Sun, 18 Mar 2012 14:43:34 -0400,
Paul Gortmaker wrote:
>
> On Sun, Mar 18, 2012 at 2:25 PM, Paul Gortmaker
> <paul.gortmaker@windriver.com> wrote:
> > Hi Takashi,
> >
> > If you have a spare moment, can you look at the following build failure?
>
> I see now that Randy already reported this. Sorry for the duplicate.
>
> http://marc.info/?l=linux-next&m=133191059601660&w=2
OK, then this should have been already fixed.
Please wait for tomorrow's linux-next tree.
thanks,
Takashi
>
> Paul.
> ---
>
> >
> > http://kisskb.ellerman.id.au/kisskb/buildresult/5884004/
> >
> > I didn't bisect to be 100% sure, but it does look like it might be
> > caused by your commit below.
> >
> > Thanks,
> > Paul.
> > ---
> >
> > commit 7907ae3e50613ae1c6d1a10f34fcd63f4123b93d
> > Author: Takashi Iwai <tiwai@suse.de>
> > Date: Wed Mar 14 08:20:20 2012 +0100
> >
> > ALSA: hda - Fix build of patch_sigmatel.c without CONFIG_SND_HDA_POWER_SAVE
> >
> > Now the mute-LED is controlled without powersave hack, and the ifdefs must
> > be removed.
> >
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-next" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2012-03-18 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 18:25 linux-next: "ALSA: hda - Fix build of patch_sigmatel.c" commit breaks sparc Paul Gortmaker
2012-03-18 18:43 ` Paul Gortmaker
2012-03-18 20:27 ` 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=s5hfwd5hcyv.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-next@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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