devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
	Stanislav Jakubek <stano.jakubek@gmail.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: mmc: brcm,kona-sdhci: convert to YAML
Date: Tue, 9 May 2023 14:20:53 -0700	[thread overview]
Message-ID: <c90f4cf0-0571-3b5d-8ea9-aa8f0ecaadec@gmail.com> (raw)
In-Reply-To: <20230509211953.1796591-1-f.fainelli@gmail.com>

On 5/9/23 14:19, Florian Fainelli wrote:
> On Mon, 8 May 2023 14:46:03 +0200, Stanislav Jakubek <stano.jakubek@gmail.com> wrote:
>> Convert Broadcom Kona family SDHCI controller bindings to DT schema.
>>
>> Changes during conversion:
>>    - also mark reg and interrupts as required
>>    - drop deprecated compatible (it's been deprecated for ~10 years)
>>
>> Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
>> ---
> 
> Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!

Sorry, that's not the one I intended to apply, dropped.
-- 
Florian


  reply	other threads:[~2023-05-09 21:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 12:45 [PATCH 1/2] ARM: dts: bcm-mobile: align SDHCI node name with bindings Stanislav Jakubek
2023-05-08 12:46 ` [PATCH 2/2] dt-bindings: mmc: brcm,kona-sdhci: convert to YAML Stanislav Jakubek
2023-05-08 19:56   ` Conor Dooley
2023-05-08 20:27   ` Krzysztof Kozlowski
2023-05-09 10:10     ` Ulf Hansson
2023-05-09 21:19   ` Florian Fainelli
2023-05-09 21:20     ` Florian Fainelli [this message]
2023-05-09 21:20 ` [PATCH 1/2] ARM: dts: bcm-mobile: align SDHCI node name with bindings Florian Fainelli

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=c90f4cf0-0571-3b5d-8ea9-aa8f0ecaadec@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=stano.jakubek@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).