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 8AD3AC4332F for ; Mon, 14 Nov 2022 09:00:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236645AbiKNJAO (ORCPT ); Mon, 14 Nov 2022 04:00:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41590 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236662AbiKNJAF (ORCPT ); Mon, 14 Nov 2022 04:00:05 -0500 Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1D5631CFFC; Mon, 14 Nov 2022 01:00:04 -0800 (PST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 21A033200919; Mon, 14 Nov 2022 04:00:03 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 14 Nov 2022 04:00:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1668416402; x=1668502802; bh=mVnSj1iJ99 XRSH8Flsh+M/LkbPmD6UmUFvX6v++TUpU=; b=a378pGvuyqgTQZMPJ5Ie0bWA+S 9tu8Bkh1p30mk6d6j01puqm61I1ytb1aXPmWMIRYJD2daavESZTmcvj34348tikd SpKk4yGahMSWbP1m4LR553pEc9i5hLdXTtl+v2i+srD6qAq/XfBfUiDjfmMrgiAK mmUrywWza5dgttnfmAmNLVmIF4H6EIWf70WvaFrO3EsyamVdONlOg0bXt1T+NEEf n+/TQV7ZgMIrlvUX6jarNJk32Vv7ksTbTkVODWfuokB0apx0wFEvly95M1qikl2l zWBOJ7t1kdIVMD958rxXGSG8NTUhsI9R9C4NgGQ8u4ijUk3yCWcrTaToTsTQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1668416402; x=1668502802; bh=mVnSj1iJ99XRSH8Flsh+M/LkbPmD 6UmUFvX6v++TUpU=; b=fCJ9vVBwAqFvg+iKECAeJX0pPiIPwvr2MPRiCCeeA7P7 yPwl9h1bzgrYLoChxID3UqZare+3OwcgeH0HHX+4C1su8318+H+sUqqYbEW8NCXu 8Fy+YfL0LTwKxzhfk9BwyR4oqmCKkzYBzZnc8MukbXilOn5wgUjcaLXcCEJNQn0e cCKp7PvfU5AWTR5YhfC+nm82lhKggjdFiNILs+5IaOgJ+LEcmcJyOzysUdk36Q5h mkMfew8AEso8hPP8gYrbsYX2Ke9NR+ugNt3w0icPNeMT7FkYaOMjGYQFqG10tu7l L/II/95/8ab9dvAyWWcn/QEPX5TDePZLKQn5RtWQfg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrgedugdduvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghg ucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepgeehue ehgfdtledutdelkeefgeejteegieekheefudeiffdvudeffeelvedttddvnecuffhomhgr ihhnpehkvghrnhgvlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmh epmhgrihhlfhhrohhmpehgrhgvgheskhhrohgrhhdrtghomh X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 14 Nov 2022 04:00:01 -0500 (EST) Date: Mon, 14 Nov 2022 09:59:57 +0100 From: Greg KH To: Andy Shevchenko Cc: Stephen Rothwell , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build failure after merge of the driver-core tree Message-ID: References: <20221114151235.01e5ff3b@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Mon, Nov 14, 2022 at 10:46:02AM +0200, Andy Shevchenko wrote: > On Mon, Nov 14, 2022 at 03:12:35PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > After merging the driver-core tree, today's linux-next build (arm > > multi_v7_defconfig) failed like this: > > > > drivers/mfd/vexpress-sysreg.c:64:51: error: initializer element is not constant > > 64 | .resources = (struct resource []) { > > | ^ > > drivers/mfd/vexpress-sysreg.c:64:51: note: (near initialization for 'vexpress_sysreg_cells[0]') > > drivers/mfd/vexpress-sysreg.c:73:51: error: initializer element is not constant > > 73 | .resources = (struct resource []) { > > | ^ > > drivers/mfd/vexpress-sysreg.c:73:51: note: (near initialization for 'vexpress_sysreg_cells[1]') > > drivers/mfd/vexpress-sysreg.c:82:51: error: initializer element is not constant > > 82 | .resources = (struct resource []) { > > | ^ > > drivers/mfd/vexpress-sysreg.c:82:51: note: (near initialization for 'vexpress_sysreg_cells[2]') > > drivers/mfd/vexpress-sysreg.c:90:51: error: initializer element is not constant > > 90 | .resources = (struct resource []) { > > | ^ > > drivers/mfd/vexpress-sysreg.c:90:51: note: (near initialization for 'vexpress_sysreg_cells[3]') > > > > Caused (probably) by commit > > > > 52c4d11f1dce ("resource: Convert DEFINE_RES_NAMED() to be compound literal") > > > > I have used the driver-core tree from next-20221111 for today. > > Fix is available here: > https://lore.kernel.org/lkml/20221113191027.2327-1-andriy.shevchenko@linux.intel.com/ Thanks, I'll pick that up now. greg k-h