From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Alec Su <ae40515@yahoo.com.tw>, Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org, robh+dt@kernel.org,
bjorn.andersson@linaro.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, y.oudjana@protonmail.com,
krzysztof.kozlowski+dt@linaro.org, agross@kernel.org,
sboyd@codeaurora.org
Subject: Re: [PATCH 2/2] dt-bindings: arm: qcom: Document xiaomi,natrium board
Date: Fri, 20 May 2022 13:54:06 +0200 [thread overview]
Message-ID: <dc883b3b-9eba-e883-cedb-e848b13cf746@linaro.org> (raw)
In-Reply-To: <7e5ecca1-aef7-ce90-7797-7f8be3b55715@yahoo.com.tw>
On 20/05/2022 03:23, Alec Su wrote:
> On 2022/5/19 21:05, Rob Herring wrote:
>> On Thu, 19 May 2022 07:41:12 +0000, Alec Su wrote:
>>> Document Xiaomi Mi 5s Plus (xiaomi-natrium) smartphone which is based on
>>> Snapdragon 821 SoC.
>
> I checked the full log. These warnings seem not the new warning caused
> by the patch series. Look like these device trees are trying to match
> with each of the compatible strings in qcom.yaml.
Yes, I'll fix them.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-05-20 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220519074112.25600-1-ae40515.ref@yahoo.com.tw>
2022-05-19 7:41 ` [PATCH 0/2] Add support for Xiaomi Mi 5s Plus Alec Su
2022-05-19 7:41 ` [PATCH 1/2] arm64: dts: qcom: msm8996-xiaomi-natrium: " Alec Su
2022-05-19 9:42 ` Krzysztof Kozlowski
2022-05-19 9:57 ` Yassine Oudjana
2022-05-19 10:01 ` Krzysztof Kozlowski
2022-05-19 10:06 ` Krzysztof Kozlowski
2022-05-19 10:36 ` Krzysztof Kozlowski
2022-05-20 1:34 ` kernel test robot
2022-05-25 2:32 ` Alec Su
2022-05-19 7:41 ` [PATCH 2/2] dt-bindings: arm: qcom: Document xiaomi,natrium board Alec Su
2022-05-19 9:36 ` Krzysztof Kozlowski
2022-05-19 13:05 ` Rob Herring
2022-05-20 1:23 ` Alec Su
2022-05-20 11:54 ` Krzysztof Kozlowski [this message]
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=dc883b3b-9eba-e883-cedb-e848b13cf746@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=ae40515@yahoo.com.tw \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=y.oudjana@protonmail.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;
as well as URLs for NNTP newsgroup(s).