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 X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B16CDC4320A for ; Fri, 30 Jul 2021 14:15:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 88C1660EBB for ; Fri, 30 Jul 2021 14:15:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239050AbhG3OPh (ORCPT ); Fri, 30 Jul 2021 10:15:37 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:54519 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230260AbhG3OPf (ORCPT ); Fri, 30 Jul 2021 10:15:35 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id C09BE5C00DD; Fri, 30 Jul 2021 10:15:30 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 30 Jul 2021 10:15:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=lPddGKCrifVr+BA75hbWtv4wZ0j MHiiFPSBlVdDOxQI=; b=f0ceLJqSgju24tQq+439fi8Lc57Jyt8Ugzj1pOPtyyH Hlgk9bjPRRl+l6BoZgcjZ/Zsz1xtzmTUhWh31Ofqfy1+LbxblLE4+T/lbLMEGte1 JTzDbmblM8GLNZitW4+8Yny87X1klt5ysRUyteUDgd6rc06YKLoi2OUh/zIpPy12 HuOFEfpp8DbFz1SH2L5FOa3/Mef73GchIdf6clz091bHoaf705RZgyYr55JOh8Dt M5B1C7z5y6Qhqr4iEBN0hB6FgUx32zExjfFAKIllSxRGhjijmsjS9EpB1ESXBwhH c8OPIvg9S/7FehzbT6dZfuBTiMFZVp+z1l4nmzvWqmw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=lPddGK CrifVr+BA75hbWtv4wZ0jMHiiFPSBlVdDOxQI=; b=B3ERpgVzdB0YexDE1KJ4gy SxblG6l2DetB3OZDyUXSz+pqjV7bnG8ihuZ0xjfsITjPBinl/gqkpylGqs+VFOGK Ui6vu3Y0uMvEJSUv6nWqCnmKXiye99B/cDSXpyLginuu4r4pSEd2n6EdRqJPDKRB qQCUJZl57F9ANuJWe6M/kqRn9NbLyCQ9OYJtR5wZ4M90IDJLQXHogLfxxx8G9AYw mkVQtTn2LgTiswIfsXBNsUuNoFwdOHUvyPPjOAqpKF7rpiiOo2DFWdu/QT2ypg2J KYZooRjqT5w9wp5/PX9izYv3toa2vMukcXLNtFnrrFHPtXtIohWtBTt/kJDfgYcg == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrheehgdejtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghgucfm jfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepveeuheejgf ffgfeivddukedvkedtleelleeghfeljeeiueeggeevueduudekvdetnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrd gtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 30 Jul 2021 10:15:30 -0400 (EDT) Date: Fri, 30 Jul 2021 16:15:27 +0200 From: Greg KH To: Mark Brown Cc: Linux Kernel Mailing List , Linux Next Mailing List , Phillip Potter Subject: Re: build failure after merge of the staging tree Message-ID: References: <20210730135340.17863-1-broonie@kernel.org> <20210730140454.GZ4670@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210730140454.GZ4670@sirena.org.uk> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 30, 2021 at 03:04:54PM +0100, Mark Brown wrote: > On Fri, Jul 30, 2021 at 04:02:41PM +0200, Greg KH wrote: > > > Ah, are you building with O= ? That might be the problem here, I think > > I had to fix up that mess with the older driver in the past... > > Yes, all the -next integration builds use O= to keep the working trees > between builds. Yup, just tested this locally, that's the issue. Let me make a patch series to fix this, thanks for the report... greg k-h