From: Mark Brown <broonie@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: linux-next: build failure after merge of the sound-asoc-fixes tree
Date: Mon, 18 Nov 2019 15:58:52 +0000 [thread overview]
Message-ID: <20191118155852.GG9761@sirena.org.uk> (raw)
In-Reply-To: <20191115093410.4a7938f5@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
On Fri, Nov 15, 2019 at 09:34:10AM +1100, Stephen Rothwell wrote:
> On Wed, 13 Nov 2019 08:10:35 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Caused by commit
> > 1d3e9077307f ("ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names.")
> > I have reverted that commit for today.
> I am still reverting that commit.
I've reverted the commit, I was a bit disappointed that none of the
Intel people responded but I see you didn't CC Pierre who sent the
commit so he won't have seen your report - I missed that due to the CC
to Liam who was also in the chain.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-11-18 15:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 21:10 linux-next: build failure after merge of the sound-asoc-fixes tree Stephen Rothwell
2019-11-14 22:34 ` Stephen Rothwell
2019-11-18 15:58 ` Mark Brown [this message]
2019-11-18 16:47 ` Pierre-Louis Bossart
2019-11-18 19:14 ` Mark Brown
2019-11-19 3:15 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-02-07 4:28 Stephen Rothwell
2025-10-23 23:19 Stephen Rothwell
2025-10-23 23:49 ` Mark Brown
2025-10-24 1:09 ` Stephen Rothwell
2025-10-27 22:34 ` Stephen Rothwell
2025-10-27 22:37 ` Stephen Rothwell
2025-10-28 11:53 ` 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=20191118155852.GG9761@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.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