From: "Sugaya, Taichi" <sugaya.taichi@socionext.com>
To: Maxime Ripard <maxime.ripard@bootlin.com>,
ARM-SoC Maintainers <arm@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: cpu: Fix JSON schema
Date: Mon, 1 Apr 2019 19:52:06 +0900 [thread overview]
Message-ID: <78bb248e-56b8-b825-e763-583f75148eb3@socionext.com> (raw)
In-Reply-To: <20190401091050.cwph7xlpv3pmkwnq@flea>
Hi Maxime,
Thanks for pointing my bug.
On 2019/04/01 18:10, Maxime Ripard wrote:
> Hi Sugaya, Arnd, Olof,
>
> On Thu, Mar 28, 2019 at 02:35:54PM -0500, Rob Herring wrote:
>> +arm-soc
>>
>> On Mon, Mar 18, 2019 at 5:05 AM Maxime Ripard <maxime.ripard@bootlin.com> wrote:
>>>
>>> Commit fd73403a4862 ("dt-bindings: arm: Add SMP enable-method for
>>> Milbeaut") added support for a new cpu enable-method, but did so using
>>> tabulations to ident. This is however invalid in the syntax, and resulted
>>> in a failure when trying to use that schemas for validation.
>>>
>>> Use spaces instead of tabs to indent to fix this.
>>>
>>> Fixes: fd73403a4862 ("dt-bindings: arm: Add SMP enable-method for Milbeaut")
>>> Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
>>> ---
>>> Documentation/devicetree/bindings/arm/cpus.yaml | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>>
>> This should be applied to arm-soc tree having the commit.
>
> Could you pick up that patch?
>
I got it.
My mission is to resubmit your fix-patch added my singned-off tag and
Rob's reviewed tag...right?
Thanks,
Sugaya Taichi
> Thanks!
> Maxime
>
> --
> Maxime Ripard, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
next prev parent reply other threads:[~2019-04-01 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 10:05 Maxime Ripard
2019-03-28 19:35 ` Rob Herring
2019-04-01 9:10 ` Maxime Ripard
2019-04-01 10:52 ` Sugaya, Taichi [this message]
2019-04-01 11:35 ` Maxime Ripard
2019-04-01 13:02 ` Sugaya, Taichi
2019-04-02 11:42 ` Sugaya, Taichi
2019-04-03 1:29 ` Sugaya, Taichi
2019-04-07 22:13 ` Olof Johansson
2019-04-08 3:35 ` Sugaya, Taichi
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=78bb248e-56b8-b825-e763-583f75148eb3@socionext.com \
--to=sugaya.taichi@socionext.com \
--cc=arm@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®