lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a0e6089b-b5a3-f9e3-fc2c-5b433553e154@linux.intel.com>
Date:   Mon, 18 Nov 2019 10:47:01 -0600
From:   Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To:     Mark Brown <broonie@...nel.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the sound-asoc-fixes
 tree



On 11/18/19 9:58 AM, Mark Brown wrote:
> 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@...b.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.

Sorry about that, the use of 'Fix' in the commit message might have 
misled Mark.
If you CC: me and also CC: alsa-devel you should get an answer without 
delay. I only noticed the issue this morning with kbuild reports.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ