Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp1009800ybb; Fri, 3 Apr 2020 16:19:55 -0700 (PDT) X-Google-Smtp-Source: APiQypK6q+01amov85o3i9tfIJcm0AXFkkc9oXJJe955KnGYENzbhRtzdpQ2K8FYirUGzNvUg31C X-Received: by 2002:a05:6830:10a:: with SMTP id i10mr8850180otp.190.1585955995281; Fri, 03 Apr 2020 16:19:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585955995; cv=none; d=google.com; s=arc-20160816; b=rNsiPH9KuN9m+RcENIFJ7zh3PAph8I4y8NnibiWZlhTWifnGLx/lA668ZcfpsL+6oo gZAArCwPDpXhDNxx60DTsLwi8nj+Et0bIZlJYzejh6bbYZFKEpya8vc2b/skXtp1/moR h/kQCSp/AaibnTv9NJJ5oB3RdxpNNvS0wgifdqMjGRqxWVNnCuE/xXIrYKNP+b3EyFm/ YULB9U00anMVYnHk+D0XVvuJWfqMu3cDPM3WnK/uNoT7b4z2TuUsWDNL7083uvmS7NC5 DJa228WvAgacKUOgswMqn1EqT9wmy8yCCU6hX0C4cWNKAeoFqz584e5/lYB/Z1wDNk33 Dygw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=xM1oCYmkMlq3+sLKqObCJMQTJsuA5Jqv8BvDLuWnBOg=; b=cgMpcyZDsOFfrmhsNsBge/ZkZt4iY4vE8EguwElOgyJeCti8JoHhyCJKWJ8UBgdAsn eCzTjaoO1rZ4ykQSDJo9p0aeUVg/c2Uj7fPFdxuVDyoX4Wk3TIbRzil+h4DvpwfxqF9Y +dzvEt5gwgeJ6yJEuJOVNEUJ89S6RMCPAT3KPG0iPODuncRAtHJ1qgym5Dw1sXVOlJn1 5zYRkwkTLkEHVEsVUICXc+A803ex84tGu+2fQ0j/UuzWGXIsyNitZhjIM+UDsjL2+bTp YB72f6EgtQKO+ww272SeQKJU9BpBY4gxCBJvcPPUDdCtYzYb0csXFR1nemlGQcTar+P+ fWxA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=A7dLnWa7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s27si4467662otg.229.2020.04.03.16.19.42; Fri, 03 Apr 2020 16:19:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=A7dLnWa7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728495AbgDCXRL (ORCPT + 99 others); Fri, 3 Apr 2020 19:17:11 -0400 Received: from mail-qt1-f193.google.com ([209.85.160.193]:35201 "EHLO mail-qt1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727829AbgDCXRL (ORCPT ); Fri, 3 Apr 2020 19:17:11 -0400 Received: by mail-qt1-f193.google.com with SMTP id e14so7998555qts.2; Fri, 03 Apr 2020 16:17:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xM1oCYmkMlq3+sLKqObCJMQTJsuA5Jqv8BvDLuWnBOg=; b=A7dLnWa7+Z0q5FgV+Q6evVSpYkzGfVpKzTzZbXGRqgARtmMgKjzwPtED+trqBiKMLB h7UOEzChdnH3BEMWS9iNQ/dw7Nrkrh5CyozQwYHCL9GGb7VMQCrr9POlKWzZ3BZfw2TZ llr1mkUPPV9JUpk142NG4xHZidaEFqcz+MieSlXgdoo2wM8iLx+soMT+mBYKbKVmL8/U GPDoJ6X/GeioSbkVZeaAnk631LuydGeUKSBpECRAN4TCDH9mMvzpQtNuFhCukQPNk410 M5pHUySiOuNxLmMqGRgLMIktjNdzgTKZyNJIla/hwnio3mPxMwzOSi0bOxIlSRMccb1M LIUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xM1oCYmkMlq3+sLKqObCJMQTJsuA5Jqv8BvDLuWnBOg=; b=CpYKuQxJTntZ2WRTvaXZcTFwk2SSxklBqSSBoFcejeuBaYIxGmuQBp2bfCC3KC/vYf Hs9M3iqErbIUwE/4uNlu5fFycVkBOjjPAIYP06yoaZ3i25pQkL4EtJmyVxUGd0oCE+WO 1mDOLj0BITsf1Q74Grmsuht8eLn58++oWTTE+9m09Sc0Nh/F5e1gtihMJMReCSKRYUd7 hpLu9q+rQIvFcTnb+ncuK/uf3OipkjEd+9p6pSXHHm9lEeQe/0fuAuwNud/WKOEN/ibB EzadSbkpIajYMYvJ3b1FX/N1yvN+cqTeuVhd+k+FqydFN+/AD+Zhxkb6oUywdDMJYL/N WvUQ== X-Gm-Message-State: AGi0PuYxzQApLoZDUHS9/NKzZ5Lc61kit1rFSIQz9gIIQ87ICTTlZPZF tOsiB8X1SIVMbndpJmJS4fQp3DqkKl32OsjDigRY X-Received: by 2002:ac8:2668:: with SMTP id v37mr3486320qtv.143.1585955829985; Fri, 03 Apr 2020 16:17:09 -0700 (PDT) MIME-Version: 1.0 References: <20200404091916.6f00a24d@canb.auug.org.au> In-Reply-To: <20200404091916.6f00a24d@canb.auug.org.au> From: Rob Herring Date: Fri, 3 Apr 2020 17:16:58 -0600 Message-ID: Subject: Re: linux-next: build warnings in Linus' tree To: Stephen Rothwell , Nicolas Saenz Julienne Cc: Russell King , Linux Next Mailing List , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org +Nicolas On Fri, Apr 3, 2020 at 4:19 PM Stephen Rothwell wrote: > > Hi all, > > Today's linux-next build of Linus' tree (arm multi_v7_defconfig) produced > these warnings: > > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format): /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-cells (2) differs from /soc (1) > > I have no idea what caused this :-( A dtc update combined with changes that landed in the above file after I tested and fixed the new warnings. Rob