From: Roger Quadros <rogerq@kernel.org>
To: ssantosh@kernel.org
Cc: lokeshvutla@ti.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v2 0/2] ARM: dts: keystone-k2*-evm: Fix mdio and dss node status
Date: Mon, 25 Oct 2021 10:38:53 +0300 [thread overview]
Message-ID: <ad7eb56d-f901-407d-5091-7e41a9d28fd3@kernel.org> (raw)
In-Reply-To: <20210825161736.ikx344bxfl5eqzgt@celibate>
Hi Santosh
On 25/08/2021 19:17, Nishanth Menon wrote:
> On 13:58-20210824, Roger Quadros wrote:
>> Hi Santosh,
>>
>> This series fixes mdio and dss status nodes from "ok" to "okay"
>>
>> As per Device Tree Specification [1], the status parameter of nodes can
>> be "okay", "disabled", etc. "ok" is not a valid parameter.
>>
>> U-boot Driver Model does not recognize status="ok" either and treats
>> the node as disabled.
>
> ^^ I suspect the above comment in the patches is to indicate side effect
> of non-compliance.
>
>>
>> [1] https://github.com/devicetree-org/devicetree-specification/releases/tag/v0.3
>>
>> cheers,
>> -roger
>>
>> Roger Quadros (2):
>> ARM: dts: keystone-k2*-evm: Fix mdio node status to "okay"
>> ARM: dts: keystone-k2g-evm: Fix dss node status to "okay"
>
>
> Reviewed-by: Nishanth Menon <nm@ti.com>
>
Is there a chance to still pull these in for -next? Thanks.
cheers,
-roger
next prev parent reply other threads:[~2021-10-25 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 10:58 Roger Quadros
2021-08-24 10:58 ` [PATCH v2 1/2] ARM: dts: keystone-k2*-evm: Fix mdio node status to "okay" Roger Quadros
2021-09-02 11:21 ` Grygorii Strashko
2021-08-24 10:58 ` [PATCH v2 2/2] ARM: dts: keystone-k2g-evm: Fix dss " Roger Quadros
2021-08-24 11:05 ` [PATCH v2 0/2] ARM: dts: keystone-k2*-evm: Fix mdio and dss node status Roger Quadros
2021-08-25 16:17 ` Nishanth Menon
2021-10-25 7:38 ` Roger Quadros [this message]
2021-09-14 12:31 ` Roger Quadros
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=ad7eb56d-f901-407d-5091-7e41a9d28fd3@kernel.org \
--to=rogerq@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=ssantosh@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®