From: "Rob Herring (Arm)" <robh@kernel.org>
To: Sayali Lokhande <quic_sayalil@quicinc.com>
Cc: conor+dt@kernel.org, andersson@kernel.org,
linux-mmc-owner@vger.kernel.org, linux-kernel@vger.kernel.org,
krzk+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, konradybcio@kernel.org
Subject: Re: [PATCH V3 1/3] dt-bindings: mmc: Add sdhci compatible for qcs8300
Date: Wed, 2 Jul 2025 09:52:23 -0500 [thread overview]
Message-ID: <175146791377.1660977.16811984013097391499.robh@kernel.org> (raw)
In-Reply-To: <20250702085927.10370-2-quic_sayalil@quicinc.com>
On Wed, 02 Jul 2025 14:29:25 +0530, Sayali Lokhande wrote:
> Document the sdhci compatible for Qualcomm qcs8300
> to support function for emmc on the Soc.
>
> Signed-off-by: Sayali Lokhande <quic_sayalil@quicinc.com>
> ---
> Documentation/devicetree/bindings/mmc/sdhci-msm.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.
If a tag was not added on purpose, please state why and what changed.
Missing tags:
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-07-02 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 8:59 [PATCH V3 0/3] Add eMMC support " Sayali Lokhande
2025-07-02 8:59 ` [PATCH V3 1/3] dt-bindings: mmc: Add sdhci compatible " Sayali Lokhande
2025-07-02 14:52 ` Rob Herring (Arm) [this message]
2025-07-03 12:19 ` Ulf Hansson
2025-07-02 8:59 ` [PATCH V3 2/3] arm64: dts: qcom: Add eMMC support " Sayali Lokhande
2025-07-03 12:47 ` Konrad Dybcio
2025-07-04 4:26 ` kernel test robot
2025-07-08 17:08 ` Konrad Dybcio
2025-07-02 8:59 ` [PATCH V3 3/3] arm64: dts: qcom: qcs8300-ride: Enable SDHC1 node Sayali Lokhande
2025-07-03 12:48 ` Konrad Dybcio
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=175146791377.1660977.16811984013097391499.robh@kernel.org \
--to=robh@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc-owner@vger.kernel.org \
--cc=quic_sayalil@quicinc.com \
/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
all inboxes | Powered by JetHome®