From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kamal Dasu <kamal.dasu@broadcom.com>,
ulf.hansson@linaro.org, linux-kernel@vger.kernel.org,
alcooperx@gmail.com, linux-arm-kernel@lists.infradead.org,
adrian.hunter@intel.com, linux-mmc@vger.kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, devicetree@vger.kernel.org
Cc: f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com,
Kamal Dasu <kdasu@broadcom.com>
Subject: Re: [V3, 1/2] dt-bindings: mmc: brcm,sdhci-brcmstb: Add support for 74165b0
Date: Sat, 9 Dec 2023 18:06:14 +0100 [thread overview]
Message-ID: <162c94cd-ee95-43c5-a2d1-46f9b35b1a87@linaro.org> (raw)
In-Reply-To: <20231209165816.39044-1-kamal.dasu@broadcom.com>
On 09/12/2023 17:58, Kamal Dasu wrote:
> From: Kamal Dasu <kdasu@broadcom.com>
>
> With newer sdio controller core used for 74165b0 we need to update
> the compatibility with "brcm,bcm74165b0-sdhci".
Please use standard email subjects, so with the PATCH keyword in the
title. `git format-patch` helps here to create proper versioned patches.
Another useful tool is b4. Skipping the PATCH keyword makes filtering of
emails more difficult thus making the review process less convenient.
Your v2 was already made this error. I expected v3 will be correct.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-09 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 16:58 [V3, 1/2] dt-bindings: mmc: brcm,sdhci-brcmstb: Add support for 74165b0 Kamal Dasu
2023-12-09 16:58 ` [V3, 2/2] mmc: add new sdhci reset sequence for brcm 74165b0 Kamal Dasu
2023-12-09 17:03 ` Krzysztof Kozlowski
2023-12-14 11:51 ` Adrian Hunter
2023-12-09 17:05 ` [V3, 1/2] dt-bindings: mmc: brcm,sdhci-brcmstb: Add support for 74165b0 Krzysztof Kozlowski
2023-12-09 17:06 ` Krzysztof Kozlowski [this message]
2023-12-09 18:14 ` Rob Herring
2023-12-10 4:18 ` kernel test robot
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=162c94cd-ee95-43c5-a2d1-46f9b35b1a87@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=alcooperx@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=kamal.dasu@broadcom.com \
--cc=kdasu@broadcom.com \
--cc=krzysztof.kozlowski+dt@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).