From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BD20FC433EF for ; Wed, 6 Jul 2022 12:13:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233638AbiGFMNt (ORCPT ); Wed, 6 Jul 2022 08:13:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45840 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233650AbiGFMNb (ORCPT ); Wed, 6 Jul 2022 08:13:31 -0400 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 197BD2A26C; Wed, 6 Jul 2022 05:13:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1657109595; x=1688645595; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=7/DjKhzqPO6N9gYPLVQhK1qL9CR/OpZCf7mHqFkJWdk=; b=TF7+Df6RhcribkPG/46JhHPCv2Pxetqu1G9QVpobebNCCPryE6OYJmwr oXry6gN+/H8YDqL2B9KBd5FxqXpKQ1QpLWmG52WbCym+ftQRiugSoHHrn xI0huwel3kydtCx5YYvmu/t5ILuW2afjQ6+6PYU+yxh57QRdoxzAivvCi lwU4RMb6gU08JuNswoJhj44r4dmui+UlweBMmiWqYxqR1XT8Y0dZ2uzGT nf9wyb12PLcOHH+jqlHtooOTt78Xy40d9hifvFp0Vv3drO1nKGc0svemz 1cwGfAO0K/W+kB92arE+Tyt6CQfhRH9HxnN0UCmw6/oOgkZXvVr2VbCL6 g==; X-IronPort-AV: E=McAfee;i="6400,9594,10399"; a="272516847" X-IronPort-AV: E=Sophos;i="5.92,249,1650956400"; d="scan'208";a="272516847" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jul 2022 05:13:14 -0700 X-IronPort-AV: E=Sophos;i="5.92,249,1650956400"; d="scan'208";a="568045031" Received: from aslawinx-mobl.ger.corp.intel.com (HELO [10.99.249.46]) ([10.99.249.46]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jul 2022 05:13:13 -0700 Message-ID: <7fbae4c0-e64d-7fd5-8f8b-45ded6126c21@linux.intel.com> Date: Wed, 6 Jul 2022 14:13:10 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: linux-next: build failure after merge of the sound-asoc tree Content-Language: en-US To: Mark Brown , Stephen Rothwell Cc: Liam Girdwood , Cezary Rojewski , Linux Kernel Mailing List , Linux Next Mailing List References: <20220706115529.7deea289@canb.auug.org.au> From: =?UTF-8?Q?Amadeusz_S=c5=82awi=c5=84ski?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On 7/6/2022 2:09 PM, Mark Brown wrote: > On Wed, Jul 06, 2022 at 11:55:29AM +1000, Stephen Rothwell wrote: > >> After merging the sound-asoc tree, today's linux-next build (x86_64 >> allmodconfig) failed like this: > > Which toolchain do you use? I've been using GCC 10 since it seems to be > what Linus is using, anything else I try has tended to get spurious > failures in from his tree. I will just add that Czarek already provided a fix: https://lore.kernel.org/alsa-devel/20220706062952.251704-1-cezary.rojewski@intel.com/T/#u