From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
alsa-devel@alsa-project.org,
Karol Trzcinski <karolx.trzcinski@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: SOF: Fix build
Date: Wed, 22 Apr 2020 08:13:57 -0500 [thread overview]
Message-ID: <a2a6f2d6-62f7-8ad7-4ee2-4b3d15060fa5@linux.intel.com> (raw)
In-Reply-To: <20200422130128.GF4898@sirena.org.uk>
On 4/22/20 8:01 AM, Mark Brown wrote:
> On Wed, Apr 22, 2020 at 07:59:37AM -0500, Pierre-Louis Bossart wrote:
>> On 4/22/20 7:51 AM, Mark Brown wrote:
>
>>> As the above and Stephen's report said it shows up in allmodconfig,
>>> that's the one I tested. I'm guessing it should show up in most
>>> configurations where that code gets built.
>
>> Gah, yes, I missed this report. I still don't get how this error went
>> undetected for weeks on the SOF side, will look into this.
>> We'll resubmit the whole thing.
>
> It smells like there's a missing patch that got dropped during
> upstreaming.
No, this breaks with the SOF tree as well. Clearly our CI setup is not
good enough.
next prev parent reply other threads:[~2020-04-22 13:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 11:26 [PATCH] ASoC: SOF: Fix build Mark Brown
2020-04-22 12:11 ` Pierre-Louis Bossart
2020-04-22 12:51 ` Mark Brown
2020-04-22 12:59 ` Pierre-Louis Bossart
2020-04-22 13:01 ` Mark Brown
2020-04-22 13:13 ` Pierre-Louis Bossart [this message]
2020-04-22 13:01 ` Takashi Iwai
2020-04-22 13:09 ` Mark Brown
2020-04-22 12:16 ` 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=a2a6f2d6-62f7-8ad7-4ee2-4b3d15060fa5@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=karolx.trzcinski@linux.intel.com \
--cc=lgirdwood@gmail.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