[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a2a9a5e3-91fa-47db-907f-c69ecfb73526@microchip.com>
Date: Fri, 7 Feb 2025 07:38:28 +0000
From: <Dharma.B@...rochip.com>
To: <conor@...nel.org>
CC: <ulf.hansson@...aro.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
<conor+dt@...nel.org>, <neil.armstrong@...aro.org>, <khilman@...libre.com>,
<jbrunet@...libre.com>, <martin.blumenstingl@...glemail.com>,
<linux-mmc@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <linux-amlogic@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC v2] dt-bindings: mmc: mmc-slot: make compatible
property optional
On 06/02/25 11:57 pm, Conor Dooley wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
>
> ForwardedMessage.eml
>
> Subject:
> Re: [PATCH RFC v2] dt-bindings: mmc: mmc-slot: make compatible property
> optional
> From:
> Conor Dooley <conor@...nel.org>
> Date:
> 06/02/25, 11:57 pm
>
> To:
> Dharma Balasubiramani <dharma.b@...rochip.com>
> CC:
> Ulf Hansson <ulf.hansson@...aro.org>, Rob Herring <robh@...nel.org>,
> Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
> <conor+dt@...nel.org>, Neil Armstrong <neil.armstrong@...aro.org>, Kevin
> Hilman <khilman@...libre.com>, Jerome Brunet <jbrunet@...libre.com>,
> Martin Blumenstingl <martin.blumenstingl@...glemail.com>, linux-
> mmc@...r.kernel.org, devicetree@...r.kernel.org, linux-arm-
> kernel@...ts.infradead.org, linux-amlogic@...ts.infradead.org, linux-
> kernel@...r.kernel.org
>
>
> On Wed, Feb 05, 2025 at 09:18:40AM +0530, Dharma Balasubiramani wrote:
>> Remove the compatible property from the list of required properties and
>> mark it as optional.
>>
>> Signed-off-by: Dharma Balasubiramani<dharma.b@...rochip.com>
>> ---
>> Changes in v2:
>> - Instead of moving the compatible string to the other binding, just make it
>> optional (remove from required list).
>> - Link to v1:https://lore.kernel.org/r/20241219-mmc-slot-v1-1-
>> dfc747a3d3fb@...rochip.com
> Why is this RFC? I don't see any complaints from Rob's bot, so I am
> assuming that this actually works and the error you mentioned in the
> previously version has been resolved?
yes, it is resolved.
I used the RFC prefix because Neil requested it:
*"Just send a v2 as RFC, so we can comment on it."*
>
>> ---
>> Documentation/devicetree/bindings/mmc/mmc-slot.yaml | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/mmc/mmc-slot.yaml b/Documentation/devicetree/bindings/mmc/mmc-slot.yaml
>> index 1f0667828063..ca3d0114bfc6 100644
>> --- a/Documentation/devicetree/bindings/mmc/mmc-slot.yaml
>> +++ b/Documentation/devicetree/bindings/mmc/mmc-slot.yaml
>> @@ -29,7 +29,6 @@ properties:
>> maxItems: 1
>>
>> required:
>> - - compatible
>> - reg
>>
>> unevaluatedProperties: false
>>
>> ---
>> base-commit: 40b8e93e17bff4a4e0cc129e04f9fdf5daa5397e
>> change-id: 20241219-mmc-slot-0574889daea3
>>
>> Best regards,
>> --
>> Dharma Balasubiramani<dharma.b@...rochip.com>
>>
--
With Best Regards,
Dharma B.
Powered by blists - more mailing lists