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 E7743C433F5 for ; Wed, 5 Oct 2022 07:21:56 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229627AbiJEHVy (ORCPT ); Wed, 5 Oct 2022 03:21:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60384 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229849AbiJEHVr (ORCPT ); Wed, 5 Oct 2022 03:21:47 -0400 Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A680D75396; Wed, 5 Oct 2022 00:21:44 -0700 (PDT) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id CB7EE58045B; Wed, 5 Oct 2022 03:21:42 -0400 (EDT) Received: from imap51 ([10.202.2.101]) by compute3.internal (MEProxy); Wed, 05 Oct 2022 03:21:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arndb.de; h=cc :cc:content-transfer-encoding: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=fm2; t=1664954502; x= 1664958102; bh=hcYTWpc/3N5vEGSKaH2rpYtLEFnHbmeildrec60PXfw=; b=C 9LhZlFz5Si+YNHNT5HThHJcJyaYbICbYTsPGXLKpp/8woqw3NMi2xeaiqD+VpfIN y8Lo61lPuExELQLJJnkt2tfYeoawcR/Bli3fnQsqE0WFC5ciaClvosViML5J9k97 DA16UmM9e7YLAUTgLLZbAYCApOql+0pp0WoUUFROEoLqp6oPp8vYPT8AnPqJStUU nDjCvCETHvb+Zs9nRBylu0hxomMlovqv1OKzHGZXSWjMISLdYSyzcYlaofV/Vktg iVZ4cOhJZ/jHvzAw8Riid203h2Bralt4yYHaYAhC4qYuHhaFatY+rVM4ABrVDq39 wa2hqsF3j8NMZWIjfiaeA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :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=fm2; t=1664954502; x= 1664958102; bh=hcYTWpc/3N5vEGSKaH2rpYtLEFnHbmeildrec60PXfw=; b=Z d7uGHZpc3T5sp68MR2EmUQ15TnQYo1s/8yjPsC7g1f0zw6BKBbGh5jvZsNnKehy1 8CerLvAje3Ng7fnLi99KxV4xefAod+HiT5FMoCWlrqOayygFWGfiw+nhZOhcfxNo Hfz8D0Z3mKQvUkPmnq+AZzNnwiwtPdLTsbwpbEfyl1JW9mxqCsPP5F88mlHL8Uh6 bj4YSc9WAWlVxtCxSUb4exlicZyMr+oUSDwTHkX5v6OPF1Ed96wJlL+bFa4AdMP7 rYnTuJY7V97Tebm7VPaJxKSCmNit2cQZSHZhKifBYbDcR2i1QwKx7+chrD1sBQ/N vPhfVuq1gqx208jIGqBDw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeeivddguddulecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvvefutgfgsehtqhertderreejnecuhfhrohhmpedf tehrnhguuceuvghrghhmrghnnhdfuceorghrnhgusegrrhhnuggsrdguvgeqnecuggftrf grthhtvghrnhepgfekueelgeeigefhudduledtkeefffejueelheelfedutedttdfgveeu feefieegnecuffhomhgrihhnpehkvghrnhgvlhdrohhrghenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrrhhnugesrghrnhgusgdruggv X-ME-Proxy: Feedback-ID: i56a14606:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 60BB4B60089; Wed, 5 Oct 2022 03:21:41 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-1015-gaf7d526680-fm-20220929.001-gaf7d5266 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <20220725095913.31e859ec@canb.auug.org.au> <20220815105419.4df1005b@canb.auug.org.au> <20220831091654.45d5ed41@canb.auug.org.au> <20221005114841.4540d325@canb.auug.org.au> Date: Wed, 05 Oct 2022 09:21:21 +0200 From: "Arnd Bergmann" To: "Joel Stanley" , "Florian Fainelli" Cc: "Stephen Rothwell" , "Olof Johansson" , =?UTF-8?Q?Rafa=C5=82_Mi=C5=82ecki?= , "Linux Kernel Mailing List" , linux-next , ARM Subject: Re: linux-next: build warnings after merge of the broadcom tree Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 5, 2022, at 8:02 AM, Joel Stanley wrote: > On Wed, 5 Oct 2022 at 03:01, Florian Fainelli w= rote: >> >> I am still seeing these warnings. >> >> >> >> The above commit is now >> >> >> >> 61dc1e3850a6 ("ARM: dts: BCM5301X: Add basic PCI controller pro= perties") >> > >> > Has any progress been made with this? This commit is now in the >> > arm-soc tree. >> >> Yes, I was hoping to get some feedback on this patch: >> >> https://lore.kernel.org/all/20220920210213.3268525-1-f.fainelli@gmail= .com/ >> >> but I suppose being the ARM SoC maintainer I can just go ahead and pu= sh it. Sorry, I unfortunately missed this patch, and forgot about the original issue. > I'd send a revert of the change. Rafal can then re-submit a series > that fixes the dtc warnings as well as the yaml warning once they have > been tested and reviewed. > > The yaml warnings aren't seen by other developers, as they require the > tools to be installed, but those from dtc are. Agreed. Alternatively, we could just remove the pcie@ nodes from bcm5301x as a hotfix, as they are clearly not usable in the current form, and none of the three versions (5.19, Rafa=C5=82's patch missing ranges, and Florian's patch with incorrect ranges) actually conform to the binding. I'll tentatively apply the revert for now so I can send the pull request tonight. If someone comes up with a better fix, I can use that instead. Arnd