From: Mark Brown <broonie@kernel.org>
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: ALSA development <alsa-devel@alsa-project.org>,
robh+dt@kernel.org, devicetree@vger.kernel.org,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Benson Leung <bleung@google.com>,
Gwendal Grignou <gwendal@google.com>,
Nicolas Boichat <drinkcat@google.com>,
Jimmy Cheng-Yi Chiang <cychiang@google.com>,
Dylan Reid <dgreid@google.com>
Subject: Re: [PATCH v4 07/10] ASoC: cros_ec_codec: support WoV
Date: Fri, 18 Oct 2019 19:42:38 +0100 [thread overview]
Message-ID: <20191018184238.GD4828@sirena.co.uk> (raw)
In-Reply-To: <CA+Px+wXCjaP1uktHLffRCe2C1P_D21f2+A=HDdhutoGv-BVzZQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
On Sat, Oct 19, 2019 at 02:39:20AM +0800, Tzung-Bi Shih wrote:
> Could you tell me how you get the .config (to enhance my local build
> tests next time)? I tried randconfig several times but it seems not
> easy to hit the case (i.e. CROS_EC_CODEC=y but CRYPTO_*=n).
That one was caught using merge_config.sh to merge in the config below
then have a script that turns on all options in my subsystems and MFD.
CONFIG_COMPILE_TEST=y
CONFIG_OF=y
CONFIG_I2C=y
CONFIG_SPI=y
CONFIG_REGULATOR=y
CONFIG_SOUND=y
CONFIG_SND=y
CONFIG_SND_SOC=y
CONFIG_SND_SOC_ALL_CODECS=y
CONFIG_SPMI=y
CONFIG_NLS=y
CONFIG_SLIMBUS=y
CONFIG_CLK=y
CONFIG_DMADEVICES=y
CONFIG_PCI=y
CONFIG_ACPI=y
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-10-18 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191017213539.00-tzungbi@google.com>
[not found] ` <20191017213539.07.I5388b69a7a9c551078fed216a77440cee6dedf49@changeid>
2019-10-18 17:22 ` [PATCH v4 07/10] ASoC: cros_ec_codec: support WoV Mark Brown
2019-10-18 18:39 ` Tzung-Bi Shih
2019-10-18 18:42 ` Mark Brown [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=20191018184238.GD4828@sirena.co.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bleung@google.com \
--cc=cychiang@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dgreid@google.com \
--cc=drinkcat@google.com \
--cc=enric.balletbo@collabora.com \
--cc=gwendal@google.com \
--cc=robh+dt@kernel.org \
--cc=tzungbi@google.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;
as well as URLs for NNTP newsgroup(s).