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: [PATCH v4 1/2] dt-bindings: mmc: brcm,sdhci-brcmstb: Add support for 74165b0
Date: Tue, 19 Dec 2023 08:21:17 +0100 [thread overview]
Message-ID: <61c15b50-5bb9-4288-a2dd-efc695f4a6f6@linaro.org> (raw)
In-Reply-To: <20231218210705.38201-2-kamal.dasu@broadcom.com>
On 18/12/2023 22:07, 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".
>
> Signed-off-by: Kamal Dasu <kdasu@broadcom.com>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202312101146.IK4Nrw1S-lkp@intel.com/
What was reported by robot? New SoC? You already received such feedback!
This does not make any sense.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-12-19 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 21:07 [PATCH v4 0/2] mmc: add new sdhci reset sequence for brcm 74165b0 Kamal Dasu
2023-12-18 21:07 ` [PATCH v4 1/2] dt-bindings: mmc: brcm,sdhci-brcmstb: Add support for 74165b0 Kamal Dasu
2023-12-19 7:21 ` Krzysztof Kozlowski [this message]
2023-12-18 21:07 ` [PATCH v4 2/2] mmc: add new sdhci reset sequence for brcm 74165b0 Kamal Dasu
2023-12-19 7:22 ` Krzysztof Kozlowski
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=61c15b50-5bb9-4288-a2dd-efc695f4a6f6@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
all inboxes | Powered by JetHome®