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=-11.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 6AC45C10F27 for ; Tue, 10 Mar 2020 22:03:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3A7F2222C4 for ; Tue, 10 Mar 2020 22:03:23 +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="I20JsyOJ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727788AbgCJWDW (ORCPT ); Tue, 10 Mar 2020 18:03:22 -0400 Received: from mail-wm1-f66.google.com ([209.85.128.66]:40026 "EHLO mail-wm1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727313AbgCJWDV (ORCPT ); Tue, 10 Mar 2020 18:03:21 -0400 Received: by mail-wm1-f66.google.com with SMTP id e26so3113372wme.5 for ; Tue, 10 Mar 2020 15:03:19 -0700 (PDT) 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=dYEP1uE4NnVFr/AeDKddTWSxJgA20EPFg2G+JAahXU0=; b=I20JsyOJIesiZZQ8aV/IdyM+r4UI4cQUwV9OU88GjMqXQdcGxyWCcTu+TKnMpQTwzR 8zsRR1Ku3VvKEiqj1/PL8R5Nrk6wcQBvAnxyWKr7fOA7HdZ08IH0zfDTMBnRXrE4sv+B 1FJbyCwTIoyCOqD2c6zdL2IiWQINHKswybaSp4LQ7NJ/mx5atiVaaCA7KJmFqkI1NxgO ZLyx0BgypSHUQzKXHvqeJWj1ZAU41f5jkODNqWwySdRgLuSbY/bjut3UAN1jCydVdFW5 4q0nzPNiNsFhSQ2UmsMYO7SYzoSm7Xv0C8TZTspbL4HFRap19/7Ybum6IG+LQMJ662fW FIwg== 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=dYEP1uE4NnVFr/AeDKddTWSxJgA20EPFg2G+JAahXU0=; b=cx6q3wtV5rK5olNleG9tGP01zvTmg1uho0az65G/sAXEMuCk96skzyeOACN6Qpt6ln QoJgBICdrbtkAB5oh6I2dPPSKMeVCvbkrkDxadd7w6nFOzT7Oi1OdeL1Y4wOclw4jRC3 EBe9IT4GxpC7AkW75wx6YmnhKkQTXR0TGFwjUabzL6cIBjPy/bPMr6faGywFxFkgP1Qg XxUvxf3hKBJjGp09o+iFeQklLlgURdMl/tMp4RTbPn81EwJ+Wt4Xr1FNDCC3HlZb7T/s jaeiacbwPysGedj5O/uGfHl1K+MRQqqFIm/K0m516QTnVzdArjMRxN0Aa/Bce+IrKGSk G5ng== X-Gm-Message-State: ANhLgQ3Yn4bbL3f1p1N/MmrwE81UiV+lOyESyIfs6JRQY9k5D3D4wLgG O1A2guTUlGDRPGJKgDcj2XFBMw== X-Google-Smtp-Source: ADFU+vsFsnumgp9VoOGVYqCrNLZ5ay6csw80CWgZBfUy0rM6bs6wjkEgt0Ofqq4WtgfmKA4Ub4RhiQ== X-Received: by 2002:a1c:4e14:: with SMTP id g20mr3853268wmh.143.1583877798471; Tue, 10 Mar 2020 15:03:18 -0700 (PDT) Received: from localhost (c-71-197-186-152.hsd1.wa.comcast.net. [71.197.186.152]) by smtp.gmail.com with ESMTPSA id w67sm1892315wmb.41.2020.03.10.15.03.17 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 10 Mar 2020 15:03:17 -0700 (PDT) From: Kevin Hilman To: Rob Herring List-Id: Cc: Jianxin Pan , "open list\:ARM\/Amlogic Meson..." , SoC Team , Stephen Rothwell , devicetree@vger.kernel.org, Neil Armstrong , Jerome Brunet , Martin Blumenstingl , "open list\:THERMAL" , "linux-kernel\@vger.kernel.org" , "moderated list\:ARM\/FREESCALE IMX \/ MXC ARM ARCHITECTURE" Subject: Re: [PATCH v2] dt-bindings: power: Fix dt_binding_check error In-Reply-To: References: <1583164448-83438-1-git-send-email-jianxin.pan@amlogic.com> <7hsgiqra5x.fsf@baylibre.com> Date: Tue, 10 Mar 2020 15:03:15 -0700 Message-ID: <7h36afn9zw.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 Rob Herring writes: > On Mon, Mar 2, 2020 at 10:31 AM Kevin Hilman wrote: >> >> Hi Jianxin, >> >> Jianxin Pan writes: >> >> > Missing ';' in the end of secure-monitor example node. >> > >> > Fixes: 165b5fb294e8 ("dt-bindings: power: add Amlogic secure power domains bindings") >> > Reported-by: Rob Herring >> > Signed-off-by: Jianxin Pan >> > --- >> > 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>; >> > }; >> > - } >> > + }; >> >> Thanks for the fix. Queued for v5.7. >> >> @Arnd, @Olof: you can ignore this one. I requested Jianxin to send to >> you thinking this was a fix for something you already queued, but it's >> not. I'll handle it. > > Someone has what needs fixing queued in linux-next, but this fix is > still not there. Somehow it seems like features show up in linux-next > faster than fixes for SoC tree... The fix (this patch) is queued in my 'for-next' branch which I pushed yesterday. I guess it missed next-20200310 but should be in tomorrow. Kevin [1] https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git/log/?h=for-next 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=-9.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MENTIONS_GIT_HOSTING,PDS_HP_HELO_NORDNS,RDNS_NONE, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_NONE,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail-wm1-f66.google.com ([209.85.128.66]:40026 "EHLO mail-wm1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727313AbgCJWDV (ORCPT ); Tue, 10 Mar 2020 18:03:21 -0400 Received: by mail-wm1-f66.google.com with SMTP id e26so3113372wme.5 for ; Tue, 10 Mar 2020 15:03:19 -0700 (PDT) From: Kevin Hilman To: Rob Herring Cc: Jianxin Pan , "open list\:ARM\/Amlogic Meson..." , SoC Team , Stephen Rothwell , devicetree@vger.kernel.org, Neil Armstrong , Jerome Brunet , Martin Blumenstingl , "open list\:THERMAL" , "linux-kernel\@vger.kernel.org" , "moderated list\:ARM\/FREESCALE IMX \/ MXC ARM ARCHITECTURE" Subject: Re: [PATCH v2] dt-bindings: power: Fix dt_binding_check error In-Reply-To: References: <1583164448-83438-1-git-send-email-jianxin.pan@amlogic.com> <7hsgiqra5x.fsf@baylibre.com> Date: Tue, 10 Mar 2020 15:03:15 -0700 Message-ID: <7h36afn9zw.fsf@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: Message-ID: <20200310220315.xvD08fsSOARkF9DsuGnbadohp6kj581dl1BE3KafdDo@z> Rob Herring writes: > On Mon, Mar 2, 2020 at 10:31 AM Kevin Hilman wrote: >> >> Hi Jianxin, >> >> Jianxin Pan writes: >> >> > Missing ';' in the end of secure-monitor example node. >> > >> > Fixes: 165b5fb294e8 ("dt-bindings: power: add Amlogic secure power domains bindings") >> > Reported-by: Rob Herring >> > Signed-off-by: Jianxin Pan >> > --- >> > 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>; >> > }; >> > - } >> > + }; >> >> Thanks for the fix. Queued for v5.7. >> >> @Arnd, @Olof: you can ignore this one. I requested Jianxin to send to >> you thinking this was a fix for something you already queued, but it's >> not. I'll handle it. > > Someone has what needs fixing queued in linux-next, but this fix is > still not there. Somehow it seems like features show up in linux-next > faster than fixes for SoC tree... The fix (this patch) is queued in my 'for-next' branch which I pushed yesterday. I guess it missed next-20200310 but should be in tomorrow. Kevin [1] https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git/log/?h=for-next