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=-6.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 10530C3F2CD for ; Sat, 29 Feb 2020 16:29:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D77BB2468E for ; Sat, 29 Feb 2020 16:29:12 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=baylibre-com.20150623.gappssmtp.com header.i=@baylibre-com.20150623.gappssmtp.com header.b="SIEnl2c4" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727283AbgB2Q3G (ORCPT ); Sat, 29 Feb 2020 11:29:06 -0500 Received: from mail-wm1-f67.google.com ([209.85.128.67]:40793 "EHLO mail-wm1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727119AbgB2Q3F (ORCPT ); Sat, 29 Feb 2020 11:29:05 -0500 Received: by mail-wm1-f67.google.com with SMTP id e26so1061837wme.5 for ; Sat, 29 Feb 2020 08:29:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=/nhS7fRXWHjddQ2mW6qgUCBhU766o/FgbNANhrsBC+c=; b=SIEnl2c4LTlz56TnuowihDkAwHNgn0iRVkJm3p3VjdUo+NAOW0iAVBgUQCS93z+qC0 NT/o0F4dGyDIfEKjqkkST4MXWGElsz0Ms3ijH4V1bTcuhOe2N/ISC7T3Pw33rNt1yb6i GoLFZG5G0clR5UIczr7iKW2GGVbFANq8SyTJzqmqYAgJBEFmyOo0FEBRgbcFXLdiVt9Q UpniXAW9a39DtmI3q75R0yMYdeZHZEwOc8LSKN3YTICHjqoYUuBiPT1nralowAP0Tnnv u38Hk6QCZptvhO+2BwbnflrKwueq3HYZMib9xY/OO2HWHKK8aubquWy/I7h3o0bMu9Kk X00w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=/nhS7fRXWHjddQ2mW6qgUCBhU766o/FgbNANhrsBC+c=; b=ToMQV6hrblg8M0VpAF1eMvqX1Jqv3mXGnLfI2Osqqnk+wgv6da1Ems+Az7GVNeTUwZ fQWwFHNp4cuGCJTqUwCBSYWNzeff/flPTGPBDhWZ/YPXMHnvldf2YNv/q9fikh+SLsNW IqEcO//uKmxm8YNqcLf+N9sVAo+TXmO7syY0oAU0aFj/WOFsyNr1ct43dnGovrG/ZazB p3E2Xj5/MmQUD1IZXN1Z/rmr9VUmPFfauAVbLKjLMr4LARkcN6Zu7hhDT5i0X2mcDyyi ba+MWZU/ZDormByv2ZOUMHaRhqemcq7uiW1ajbOtAPZ72tDP+ZEcIwGlCDRqVDDsk/2R simw== X-Gm-Message-State: APjAAAVGupJ5SiqHzqYfRUtciOZw8XpYhWgeNjbF94XGPElGpoSRWl8Y xjcZTXJZzAY6zeWoX2F0Kn07Uw== X-Google-Smtp-Source: APXvYqzfqcYtCrS+L+2YW0wCapvE4z22/nu0RMLPxck3ioY80N+w/B/BrxC//vE2fGmjFlcQRyFnqA== X-Received: by 2002:a7b:cc6a:: with SMTP id n10mr10430395wmj.170.1582993741675; Sat, 29 Feb 2020 08:29:01 -0800 (PST) Received: from localhost (229.3.136.88.rev.sfr.net. [88.136.3.229]) by smtp.gmail.com with ESMTPSA id k7sm18113920wrq.12.2020.02.29.08.29.00 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 29 Feb 2020 08:29:00 -0800 (PST) From: Kevin Hilman To: Jianxin Pan , Stephen Rothwell , linux-amlogic@lists.infradead.org Cc: Jianxin Pan , Rob Herring , devicetree@vger.kernel.org, Neil Armstrong , Jerome Brunet , Martin Blumenstingl , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH RESEND] dt-bindings: power: Fix dt_binding_check error In-Reply-To: <1582856099-105484-1-git-send-email-jianxin.pan@amlogic.com> References: <1582856099-105484-1-git-send-email-jianxin.pan@amlogic.com> Date: Sat, 29 Feb 2020 17:28:59 +0100 Message-ID: <7h5zfpbbn8.fsf@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jianxin, Jianxin Pan writes: > Missing ';' in the end of secure-monitor example node. > > Fixes: f50b4108ede1 ("dt-bindings: power: add Amlogic secure power domains bindings") Thanks for the fix, but where did this commit ID come from? I think this is the right upstream commit: Fixes: 165b5fb294e8 ("dt-bindings: power: add Amlogic secure power domains bindings") Also, when you resend, can you cc soc@kernel.org. The soc maintainers are who queue my amlogic tree. I will ack and they can submit to Linus for v5.7 so Stephen doesn't have to carry his local linux-next fix anymore. Thanks, Kevin > Reported-by: Rob Herring > Signed-off-by: Jianxin Pan > Reviewed-by: Neil Armstrong > Acked-by: Rob Herring > --- > Documentation/devicetree/bindings/power/amlogic,meson-sec-pwrc.yaml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/power/amlogic,meson-sec-pwrc.yaml b/Documentation/devicetree/bindings/power/amlogic,meson-sec-pwrc.yaml > index af32209..bc4e037 100644 > --- a/Documentation/devicetree/bindings/power/amlogic,meson-sec-pwrc.yaml > +++ b/Documentation/devicetree/bindings/power/amlogic,meson-sec-pwrc.yaml > @@ -36,5 +36,5 @@ examples: > compatible = "amlogic,meson-a1-pwrc"; > #power-domain-cells = <1>; > }; > - } > + }; > > -- > 2.7.4