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 D30A4C43217 for ; Tue, 14 Dec 2021 18:29:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234363AbhLNS27 (ORCPT ); Tue, 14 Dec 2021 13:28:59 -0500 Received: from mail-ot1-f52.google.com ([209.85.210.52]:34420 "EHLO mail-ot1-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230203AbhLNS26 (ORCPT ); Tue, 14 Dec 2021 13:28:58 -0500 Received: by mail-ot1-f52.google.com with SMTP id x19-20020a9d7053000000b0055c8b39420bso21893205otj.1; Tue, 14 Dec 2021 10:28:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=ec7FIqDV1eh0nWs0ieSF7kRvELIz9yZoti3SZMyr6Z4=; b=Yb8VtNnlDrON1A+So8NwWB0vKHt5rFGe4uGT1nvRq6ewd7x3LZT3aDKMP2OjkOLZxS /xeIMxyHGVT87njQyPDYNHieQl0xnNqbuvFGG28C5Uv14NgjAYXjMkqFvIzcwF5DGo/j HFfFQePw9vOkkKBdDE3aGf/9NK6ax7wfckuMY5xB8C9q+bkaaBLi8Fi0tn54P6TufdP6 OGOMfPIVHY8kJEY+wGM5ijXL1VA/dmvcyIVwMn/s7z4mAX2kCjZMhgndVWiqjIgSQw/B uaF4snfVSLwG38V4d93f3yMDjgG8BZSkda3vc5jEouAKEMqS+vEc18NKe6HyNpK0sOXf G9xg== X-Gm-Message-State: AOAM533ACC+4r+V3Sf0emdFyEQ3udBmszBdCnn9PrznwU7qQ1uZChgth sCxnR+SA/J8QM6yoHhnkPA== X-Google-Smtp-Source: ABdhPJzUem8yjSvP+Lgu17uRUc1SGESD4X7Fx0l1fGs6fceVyZYQPmbVY5NFkIQsvgkwjlyGy+WB2g== X-Received: by 2002:a05:6830:4428:: with SMTP id q40mr5526277otv.171.1639506537308; Tue, 14 Dec 2021 10:28:57 -0800 (PST) Received: from robh.at.kernel.org (66-90-148-213.dyn.grandenetworks.net. [66.90.148.213]) by smtp.gmail.com with ESMTPSA id 16sm112932oix.46.2021.12.14.10.28.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Dec 2021 10:28:56 -0800 (PST) Received: (nullmailer pid 3683781 invoked by uid 1000); Tue, 14 Dec 2021 18:28:54 -0000 Date: Tue, 14 Dec 2021 12:28:54 -0600 From: Rob Herring To: Florian Fainelli Cc: Alessandro Zummo , linux-pwm@vger.kernel.org, linux-mmc@vger.kernel.org, Markus Mayer , Ulf Hansson , Ray Jui , Amit Kucheria , bcm-kernel-feedback-list@broadcom.com, Greg Kroah-Hartman , linux-pm@vger.kernel.org, Doug Berger , =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= , Lee Jones , Bartosz Golaszewski , linux-usb@vger.kernel.org, Damien Le Moal , Linus Walleij , linux-ide@vger.kernel.org, Thomas Gleixner , Scott Branden , Thierry Reding , Al Cooper , Daniel Lezcano , linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Alexandre Belloni , "Rafael J. Wysocki" , Gregory Fong , linux-rtc@vger.kernel.org, Herbert Xu , Marc Zyngier , linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, Zhang Rui , Philipp Zabel , devicetree@vger.kernel.org Subject: Re: [PATCH v3 13/15] dt-bindings: ata: Convert Broadcom SATA to YAML Message-ID: References: <20211208003727.3596577-1-f.fainelli@gmail.com> <20211208003727.3596577-14-f.fainelli@gmail.com> <1638971068.770579.3857735.nullmailer@robh.at.kernel.org> 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-crypto@vger.kernel.org On Wed, Dec 08, 2021 at 09:33:38AM -0800, Florian Fainelli wrote: > On 12/8/21 5:44 AM, Rob Herring wrote: > > On Tue, 07 Dec 2021 16:37:24 -0800, Florian Fainelli wrote: > >> Convert the Broadcom SATA3 AHCI controller Device Tree binding to YAML > >> to help with validation. > >> > >> Acked-by: Damien Le Moal > >> Signed-off-by: Florian Fainelli > >> --- > >> .../bindings/ata/brcm,sata-brcm.txt | 45 --------- > >> .../bindings/ata/brcm,sata-brcm.yaml | 98 +++++++++++++++++++ > >> 2 files changed, 98 insertions(+), 45 deletions(-) > >> delete mode 100644 Documentation/devicetree/bindings/ata/brcm,sata-brcm.txt > >> create mode 100644 Documentation/devicetree/bindings/ata/brcm,sata-brcm.yaml > >> > > > > Running 'make dtbs_check' with the schema in this patch gives the > > following warnings. Consider if they are expected or the schema is > > incorrect. These may not be new warnings. > > > > Note that it is not yet a requirement to have 0 warnings for dtbs_check. > > This will change in the future. > > > > Full log is available here: https://patchwork.ozlabs.org/patch/1565011 > > Likewise, those indicate that the preceding patch which renames the sata > controller unit name has not been applied. I looked at that, but it was the unevaluated properties I was worried about. However, the example has the same thing, but no errors. I think running with DT_SCHEMA_FILES means sata-common.yaml is not included. I'll have to look into that. Rob