From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org
Subject: Re: sound/pci/hda/hda_codec.c:1435:46: error: 'AC_VERB_GET_CON' undeclared
Date: Mon, 15 Oct 2012 09:59:45 +0900 [thread overview]
Message-ID: <20121015005944.GC24935@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121014023953.GA8713@localhost>
On Sun, Oct 14, 2012 at 10:39:53AM +0800, Fengguang Wu wrote:
> OK. Takashi, Mark, the build system can now avoid testing selected
> trees during the merge window. Shall I add your trees to the list?
For me I'd really want to be able to keep the for-next branch covered,
it's better to have the false positives than to loose that coverage.
next prev parent reply other threads:[~2012-10-15 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121012170109.GD20312@localhost>
2012-10-13 8:29 ` sound/pci/hda/hda_codec.c:1435:46: error: 'AC_VERB_GET_CON' undeclared Takashi Iwai
2012-10-14 2:39 ` Fengguang Wu
2012-10-14 7:44 ` Takashi Iwai
2012-10-15 0:59 ` Mark Brown [this message]
2012-10-15 1:49 ` Fengguang Wu
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=20121015005944.GC24935@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=fengguang.wu@intel.com \
--cc=kernel-janitors@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;
as well as URLs for NNTP newsgroup(s).