All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Dharma.B@microchip.com>
To: <conor@kernel.org>
Cc: <ulf.hansson@linaro.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <neil.armstrong@linaro.org>,
	<khilman@baylibre.com>, <jbrunet@baylibre.com>,
	<martin.blumenstingl@googlemail.com>, <linux-mmc@vger.kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-amlogic@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC v2] dt-bindings: mmc: mmc-slot: make compatible property optional
Date: Fri, 7 Feb 2025 07:38:28 +0000	[thread overview]
Message-ID: <a2a9a5e3-91fa-47db-907f-c69ecfb73526@microchip.com> (raw)
In-Reply-To: <20250206-drainer-vastly-34a3c738e2bf@spud>

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@kernel.org>
> Date:
> 06/02/25, 11:57 pm
> 
> To:
> Dharma Balasubiramani <dharma.b@microchip.com>
> CC:
> Ulf Hansson <ulf.hansson@linaro.org>, Rob Herring <robh@kernel.org>, 
> Krzysztof Kozlowski <krzk+dt@kernel.org>, Conor Dooley 
> <conor+dt@kernel.org>, Neil Armstrong <neil.armstrong@linaro.org>, Kevin 
> Hilman <khilman@baylibre.com>, Jerome Brunet <jbrunet@baylibre.com>, 
> Martin Blumenstingl <martin.blumenstingl@googlemail.com>, linux- 
> mmc@vger.kernel.org, devicetree@vger.kernel.org, linux-arm- 
> kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux- 
> kernel@vger.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@microchip.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@microchip.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@microchip.com>
>>


-- 
With Best Regards,
Dharma B.

  reply	other threads:[~2025-02-07  7:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05  3:48 [PATCH RFC v2] dt-bindings: mmc: mmc-slot: make compatible property optional Dharma Balasubiramani
2025-02-05  3:48 ` Dharma Balasubiramani
2025-02-06 18:27 ` Conor Dooley
2025-02-06 18:27   ` Conor Dooley
2025-02-07  7:38   ` Dharma.B [this message]
2025-02-07  8:55 ` Neil Armstrong
2025-02-07  8:55   ` Neil Armstrong
2025-02-07  9:02   ` Dharma.B
2025-02-07  9:17     ` neil.armstrong
2025-02-07  9:17       ` neil.armstrong
2025-02-07 16:03       ` Conor Dooley
2025-02-07 16:03         ` Conor Dooley
2025-02-10  5:28       ` Dharma.B
2025-02-10  9:51         ` neil.armstrong
2025-02-10  9:51           ` neil.armstrong
2025-02-11 20:12         ` Rob Herring
2025-02-11 20:12           ` Rob Herring
2025-02-12  3:51           ` Dharma.B

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=a2a9a5e3-91fa-47db-907f-c69ecfb73526@microchip.com \
    --to=dharma.b@microchip.com \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@kernel.org \
    --cc=ulf.hansson@linaro.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.