From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: alsa-devel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Subject: Re: [PATCH] MIPS/sound: DB1200 audio support depends on MIPS arch.
Date: Thu, 10 Nov 2011 12:17:42 +0000 [thread overview]
Message-ID: <20111110121742.GE21453@linux-mips.org> (raw)
In-Reply-To: <1320924059-4142-1-git-send-email-manuel.lauss@googlemail.com>
On Thu, Nov 10, 2011 at 12:20:59PM +0100, Manuel Lauss wrote:
> DB1200 audio support should only be visible if MIPS/Alchemy arch is
> selected. Fixes an x86-allmodconfig build failure in linux-next.
>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Manuel Lauss <manuel.lauss@googlemail.com>
Thanks, folded into the offending patch.
Ralf
prev parent reply other threads:[~2011-11-10 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 1:22 linux-next: build failure after merge of the mips tree Stephen Rothwell
2011-11-10 11:20 ` [PATCH] MIPS/sound: DB1200 audio support depends on MIPS arch Manuel Lauss
2011-11-10 11:34 ` [alsa-devel] " Mark Brown
2011-11-10 11:36 ` Mark Brown
2011-11-10 11:46 ` Manuel Lauss
2011-11-10 12:17 ` Ralf Baechle [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=20111110121742.GE21453@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=alsa-devel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=manuel.lauss@googlemail.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).