linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Broadcom Kernel Team <bcm-kernel-feedback-list@broadcom.com>,
	Al Cooper <alcooperx@gmail.com>,
	linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: mmc: brcm,sdhci-brcmstb: correct number of reg entries
Date: Thu, 28 Apr 2022 08:00:21 -0700	[thread overview]
Message-ID: <e25544bd-6fc1-e5c0-79b2-71e5d51bcde2@gmail.com> (raw)
In-Reply-To: <20220428081817.35382-1-krzysztof.kozlowski@linaro.org>



On 4/28/2022 1:18 AM, Krzysztof Kozlowski wrote:
> The binding should not allow infinite number of 'reg' entries, so add
> strict limit.
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Acked-by: Florian Fainelli <f.fainelli@gmail.com>

Given Kamal's patch series:

https://lore.kernel.org/linux-devicetree/20220427180853.35970-1-kdasu.kdev@gmail.com/

we should probably merge those via Ulf's mmc tree to avoid conflicts.
-- 
Florian

  parent reply	other threads:[~2022-04-28 15:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  8:18 [PATCH 1/2] dt-bindings: mmc: brcm,sdhci-brcmstb: correct number of reg entries Krzysztof Kozlowski
2022-04-28  8:18 ` [PATCH 2/2] dt-bindings: mmc: brcm,sdhci-brcmstb: cleanup example Krzysztof Kozlowski
2022-04-28 15:00   ` Florian Fainelli
2022-05-04 10:37   ` Ulf Hansson
2022-04-28 15:00 ` Florian Fainelli [this message]
2022-05-04 10:37 ` [PATCH 1/2] dt-bindings: mmc: brcm,sdhci-brcmstb: correct number of reg entries Ulf Hansson

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=e25544bd-6fc1-e5c0-79b2-71e5d51bcde2@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=alcooperx@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).