From: Kevin Hilman <khilman@baylibre.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, Jianxin Pan <jianxin.pan@amlogic.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
SoC Team <soc@kernel.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH v2] dt-bindings: power: Fix dt_binding_check error
Date: Tue, 10 Mar 2020 15:03:15 -0700 [thread overview]
Message-ID: <7h36afn9zw.fsf@baylibre.com> (raw)
In-Reply-To: <CAL_JsqJAxfL_Q3HYHk_8VeefdXnhYT7kcPe3F5Gzk1Vfj+xtww@mail.gmail.com>
Rob Herring <robh+dt@kernel.org> writes:
> On Mon, Mar 2, 2020 at 10:31 AM Kevin Hilman <khilman@baylibre.com> wrote:
>>
>> Hi Jianxin,
>>
>> Jianxin Pan <jianxin.pan@amlogic.com> 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 <robh+dt@kernel.org>
>> > Signed-off-by: Jianxin Pan <jianxin.pan@amlogic.com>
>> > ---
>> > 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
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Jianxin Pan <jianxin.pan@amlogic.com>,
"open list\:ARM\/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>, SoC Team <soc@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
devicetree@vger.kernel.org,
Neil Armstrong <narmstrong@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
"open list\:THERMAL" <linux-pm@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"moderated list\:ARM\/FREESCALE IMX \/ MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] dt-bindings: power: Fix dt_binding_check error
Date: Tue, 10 Mar 2020 15:03:15 -0700 [thread overview]
Message-ID: <7h36afn9zw.fsf@baylibre.com> (raw)
In-Reply-To: <CAL_JsqJAxfL_Q3HYHk_8VeefdXnhYT7kcPe3F5Gzk1Vfj+xtww@mail.gmail.com>
Rob Herring <robh+dt@kernel.org> writes:
> On Mon, Mar 2, 2020 at 10:31 AM Kevin Hilman <khilman@baylibre.com> wrote:
>>
>> Hi Jianxin,
>>
>> Jianxin Pan <jianxin.pan@amlogic.com> 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 <robh+dt@kernel.org>
>> > Signed-off-by: Jianxin Pan <jianxin.pan@amlogic.com>
>> > ---
>> > 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
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, Jianxin Pan <jianxin.pan@amlogic.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
SoC Team <soc@kernel.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH v2] dt-bindings: power: Fix dt_binding_check error
Date: Tue, 10 Mar 2020 15:03:15 -0700 [thread overview]
Message-ID: <7h36afn9zw.fsf@baylibre.com> (raw)
In-Reply-To: <CAL_JsqJAxfL_Q3HYHk_8VeefdXnhYT7kcPe3F5Gzk1Vfj+xtww@mail.gmail.com>
Rob Herring <robh+dt@kernel.org> writes:
> On Mon, Mar 2, 2020 at 10:31 AM Kevin Hilman <khilman@baylibre.com> wrote:
>>
>> Hi Jianxin,
>>
>> Jianxin Pan <jianxin.pan@amlogic.com> 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 <robh+dt@kernel.org>
>> > Signed-off-by: Jianxin Pan <jianxin.pan@amlogic.com>
>> > ---
>> > 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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-10 22:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 15:54 [PATCH v2] dt-bindings: power: Fix dt_binding_check error Jianxin Pan
2020-03-02 15:54 ` Jianxin Pan
2020-03-02 15:54 ` Jianxin Pan
2020-03-02 16:31 ` Kevin Hilman
2020-03-02 16:31 ` Kevin Hilman
2020-03-02 16:31 ` Kevin Hilman
2020-03-10 20:36 ` Rob Herring
2020-03-10 20:36 ` Rob Herring
2020-03-10 22:03 ` Kevin Hilman [this message]
2020-03-10 22:03 ` Kevin Hilman
2020-03-10 22:03 ` Kevin Hilman
2020-03-02 20:15 ` Rob Herring
2020-03-02 20:15 ` Rob Herring
2020-03-02 20:15 ` Rob Herring
2020-03-03 8:43 ` Kevin Hilman
2020-03-03 8:43 ` Kevin Hilman
2020-03-03 8:43 ` Kevin Hilman
2020-03-04 16:35 ` Jianxin Pan
2020-03-04 16:35 ` Jianxin Pan
2020-03-04 16:35 ` Jianxin Pan
2020-03-04 16:34 ` Jianxin Pan
2020-03-04 16:34 ` Jianxin Pan
2020-03-04 16:34 ` Jianxin Pan
2020-03-10 0:41 ` patchwork-bot+linux-amlogic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7h36afn9zw.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=jianxin.pan@amlogic.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=soc@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.