public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <Dharma.B@microchip.com>
To: <robh@kernel.org>, <conor@kernel.org>
Cc: <ulf.hansson@linaro.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <neil.armstrong@linaro.org>,
	<khilman@baylibre.com>, <jbrunet@baylibre.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>,
	<martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH] dt-bindings: mmc: move compatible property to its specific binding
Date: Tue, 4 Feb 2025 04:24:00 +0000	[thread overview]
Message-ID: <f312c7ff-8d9b-4317-a75b-ce3d0f94a7ae@microchip.com> (raw)
In-Reply-To: <779651f3-e5d4-4de8-878a-84653735e5cb@microchip.com>

Rob / Conor,

On 20/01/25 10:00 am, Dharma B wrote:
> Hi Rob/Conor,
> 
> On 09/01/25 2:26 am, Martin Blumenstingl wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know 
>> the content is safe
>>
>> Hi Dharma,
>>
>> On Wed, Jan 8, 2025 at 4:11 AM <Dharma.B@microchip.com> wrote:
>> [...]
>>> "One issue is 'compatible' is required. Either that would have to be
>>> dropped as required."
>>>
>>> Instead of just dropping it from "required:", I removed the property
>>> itself and moved it to another binding.
>>>
>>> I will send a v2 by removing it from the required, will it be fine?
>> For me this is fine.
>>
>> My understanding is that if we drop the compatible property completely
>> then any compatible string will be allowed (for example: compatible =
>> "random,name"). This is because mmc-slot.yaml inherits the properties
>> from mmc-controller-common.yaml which itself has
>> "additionalProperties: true".
>> However, if we allow it but make it optional it means that there's
>> only two valid states:
>> - no compatible property (on the Atmel / Microchip SoCs)
>> - a compatible property with the value "mmc-slot" (as used on Amlogic
>> Meson and Cavium Thunder SoCs)
>> - (anything else is considered invalid)
>>
>> Rob, Conor: can confirm this or correct me wherever I got something 
>> wrong.
>> I hope that your feedback will help Dharma write a good patch
>> description for v2.
> 
> Shall I proceed with v2 by dropping the compatible from the required 
> property list?

I hope this email finds you well. Just following up on my previous 
message from 20/01/25, as it seems to have achieved an impressive 
feat—perfect stealth mode. Either my patch is so flawless that it left 
everyone speechless, or it has been silently sacrificed to the inbox 
gods. 😅

If there are any concerns, feedback, or a secret ritual I need to 
perform to get a response, please do let me know. Would love to hear 
your thoughts when time permits.

Looking forward to breaking the radio silence!
> 
>>
>>
>> Best regards,
>> Martin
>>
> 
> 


-- 
With Best Regards,
Dharma B.

  reply	other threads:[~2025-02-04  4:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19  4:10 [PATCH] dt-bindings: mmc: move compatible property to its specific binding Dharma Balasubiramani
2024-12-19 20:11 ` Conor Dooley
2025-01-07  3:34   ` Dharma.B
2025-01-07 20:34     ` Martin Blumenstingl
2025-01-08  3:11       ` Dharma.B
2025-01-08 20:56         ` Martin Blumenstingl
2025-01-20  4:30           ` Dharma.B
2025-02-04  4:24             ` Dharma.B [this message]
2025-02-04  8:14               ` neil.armstrong
2025-02-05  3:49                 ` 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=f312c7ff-8d9b-4317-a75b-ce3d0f94a7ae@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox