From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org, Jie Yang <yang.jie@linux.intel.com>
Subject: Re: [PATCH] ASoC: Intel: Make boards more available for compile test
Date: Thu, 11 Apr 2019 12:01:15 +0100 [thread overview]
Message-ID: <20190411110115.GC7953@sirena.org.uk> (raw)
In-Reply-To: <765c0d7b-8589-b1ba-3592-59ecb0cc22d0@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 662 bytes --]
On Wed, Apr 10, 2019 at 01:05:40PM -0500, Pierre-Louis Bossart wrote:
> On 4/10/19 11:38 AM, Mark Brown wrote:
> > The Intel boards have very strict dependencies which make them less
> > available for compile test than is desirable, with requirements for
> > specific drivers that are only needed at runtime but not at build time.
> > Relax this a bit if COMPILE_TEST is enabled to improve build coverage
> > for these drivers.
> It's really asking for trouble but it's the right thing to do. Let's see how
> many issues get reported...
It's probably fine, they get covered by allmodconfig already - it
certainly didn't immediately trigger any issues for me.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2019-04-11 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 16:38 [PATCH] ASoC: Intel: Make boards more available for compile test Mark Brown
2019-04-10 18:05 ` Pierre-Louis Bossart
2019-04-11 11:01 ` Mark Brown [this message]
2019-04-11 11:19 ` Applied "ASoC: Intel: Make boards more available for compile test" to the asoc tree Mark Brown
2019-05-02 2:18 ` Mark Brown
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=20190411110115.GC7953@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=yang.jie@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.