From: <Dharma.B@microchip.com>
To: <krzk@kernel.org>
Cc: <ulf.hansson@linaro.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <Nicolas.Ferre@microchip.com>,
<alexandre.belloni@bootlin.com>, <claudiu.beznea@tuxon.dev>,
<Aubin.Constans@microchip.com>, <linux-mmc@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] dt-bindings: mmc: atmel,sama5d2-sdhci: Add sama7d65 compatible
Date: Sat, 31 Aug 2024 07:51:15 +0000 [thread overview]
Message-ID: <44e7a3a4-52f9-4985-b2dd-2bcf35d34737@microchip.com> (raw)
In-Reply-To: <3wysn3i3syox3n7howwnewuy6h7457goeafbrilptewxyuqitr@cdyjlzp5s7bu>
Hi Krzysztof,
On 31/08/24 11:50 am, Krzysztof Kozlowski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Fri, Aug 30, 2024 at 08:21:21PM +0530, Dharma Balasubiramani wrote:
>> Add mmc binding documentation for sama7d65.
>>
>> Signed-off-by: Dharma Balasubiramani <dharma.b@microchip.com>
>> ---
>> Documentation/devicetree/bindings/mmc/atmel,sama5d2-sdhci.yaml | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>
> Where is any user of this? Why are you adding bindings without users?
We will upstream the sama7d65 board dts files soon, hence adding support
for it before hand in bindings.
>
> Best regards,
> Krzysztof
>
--
With Best Regards,
Dharma B.
next prev parent reply other threads:[~2024-08-31 7:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 14:51 [PATCH v3 0/2] Update sdhci-atmel dt-binding documentation Dharma Balasubiramani
2024-08-30 14:51 ` [PATCH v3 1/2] dt-bindings: mmc: sdhci-atmel: Convert to json schema Dharma Balasubiramani
2024-08-31 6:19 ` Krzysztof Kozlowski
2024-08-31 7:47 ` Dharma.B
2024-08-30 14:51 ` [PATCH v3 2/2] dt-bindings: mmc: atmel,sama5d2-sdhci: Add sama7d65 compatible Dharma Balasubiramani
2024-08-31 6:20 ` Krzysztof Kozlowski
2024-08-31 7:51 ` Dharma.B [this message]
2024-08-31 13:41 ` Krzysztof Kozlowski
2024-09-02 10:40 ` 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=44e7a3a4-52f9-4985-b2dd-2bcf35d34737@microchip.com \
--to=dharma.b@microchip.com \
--cc=Aubin.Constans@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.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