From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Bhupesh Sharma <bhupesh.sharma@linaro.org>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
abel.vesa@linaro.org, Johan Hovold <johan+linaro@kernel.org>
Subject: Re: [PATCH 4/5] dt-bindings: mmc: sdhci-msm: drop properties mentioned in common MMC
Date: Mon, 5 Dec 2022 16:11:10 -0600 [thread overview]
Message-ID: <20221205221110.GA2754803-robh@kernel.org> (raw)
In-Reply-To: <20221204094717.74016-4-krzysztof.kozlowski@linaro.org>
On Sun, Dec 04, 2022 at 10:47:16AM +0100, Krzysztof Kozlowski wrote:
> There is no need to explicitly list properties already brought by
> mmc-controller.yaml schema.
>
> Fixes: 8574adf5222d ("dt-bindings: mmc: sdhci-msm: Fix issues in yaml bindings")
Redundant, but not broken.
With 'Fixes' dropped,
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-12-05 22:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 9:47 [PATCH 1/5] dt-bindings: mmc: sdhci: document sdhci-caps and sdhci-caps-mask Krzysztof Kozlowski
2022-12-04 9:47 ` [PATCH 2/5] dt-bindings: mmc: sdhci-am654: cleanup style Krzysztof Kozlowski
2022-12-05 22:08 ` Rob Herring
2022-12-04 9:47 ` [PATCH 3/5] dt-bindings: mmc: sdhci-msm: " Krzysztof Kozlowski
2022-12-05 22:09 ` Rob Herring
2022-12-04 9:47 ` [PATCH 4/5] dt-bindings: mmc: sdhci-msm: drop properties mentioned in common MMC Krzysztof Kozlowski
2022-12-05 22:11 ` Rob Herring [this message]
2022-12-04 9:47 ` [PATCH 5/5] dt-bindings: mmc: sdhci-msm: allow dma-coherent Krzysztof Kozlowski
2022-12-05 22:11 ` Rob Herring
2022-12-07 12:37 ` Ulf Hansson
2022-12-05 22:08 ` [PATCH 1/5] dt-bindings: mmc: sdhci: document sdhci-caps and sdhci-caps-mask Rob Herring
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=20221205221110.GA2754803-robh@kernel.org \
--to=robh@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=andersson@kernel.org \
--cc=bhupesh.sharma@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.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.