From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Karol Trzcinski <karolx.trzcinski@linux.intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: SOF: Fix build
Date: Wed, 22 Apr 2020 07:11:26 -0500 [thread overview]
Message-ID: <2c307fac-077e-6692-a57a-2c2084a4742f@linux.intel.com> (raw)
In-Reply-To: <20200422112602.13109-1-broonie@kernel.org>
On 4/22/20 6:26 AM, Mark Brown wrote:
> The recent batch of SOF changes failed to build on some x86
> configurations including an allmodconfig, revert the commits:
>
> e150ef4169a76 ASoC: SOF: Introduce extended manifest
> 371091417864b ASoC: SOF: ext_manifest: parse firmware version
> 7c024b948c206 ASoC: SOF: ext_manifest: parse compiler version
> 9e72f13ee541c ASoC: SOF: ext_manifest: parse windows
>
> to fix this.
Not sure what happened here, these patches were held for a rather long
time in the SOF tree, I haven't seen any kbuild report or email on this?
We'll fix 'this' but if there's a pointer on what configurations failed
that would be nice to know.
Thanks
-Pierre
next prev parent reply other threads:[~2020-04-22 12:12 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 [this message]
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
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=2c307fac-077e-6692-a57a-2c2084a4742f@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