From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: forbidden405@foxmail.com, 'Andy Gross' <agross@kernel.org>,
'Bjorn Andersson' <andersson@kernel.org>,
'Konrad Dybcio' <konrad.dybcio@linaro.org>,
'Rob Herring' <robh+dt@kernel.org>,
'Krzysztof Kozlowski' <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: msm8916-zhihe: Add initial device tree for zhihe Wifi/LTE dongle UFI-001C and uf896
Date: Tue, 10 Jan 2023 19:29:25 +0100 [thread overview]
Message-ID: <f909c1b0-97db-cc33-fa27-c5e901f11956@linaro.org> (raw)
In-Reply-To: <tencent_98E029F744FE85B9FD68B570A45A01743F07@qq.com>
On 10/01/2023 19:17, forbidden405@foxmail.com wrote:
> Thanks for your review, but I don't know how to deal with such a
> device with unknown vendor. Do you have any idea and show me
> some possible solutions? If "zhihe" is dropped, what can be a substitute?
Please do not remove the context you are replying to.
You install this kernel with DTB on some device so clearly you have such
device in hand, right? It has then some manufacturer, some company. If
it is USB stick as you said, then it has even vendor ID, which might be
or might not be real.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-10 18:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230110155014.31664-1-forbidden405@foxmail.com>
2023-01-10 15:50 ` [PATCH 1/3] dt-bindings: vendor-prefixes: add zhihe Yang Xiwen
2023-01-10 16:32 ` Krzysztof Kozlowski
2023-01-10 15:50 ` [PATCH 2/3] dt-bindings: qcom: Ducument bindings for new msm8916-zhihe-uf896 and msm8916-zhihe-ufi001c Yang Xiwen
2023-01-10 16:31 ` Krzysztof Kozlowski
2023-01-10 15:50 ` [PATCH 3/3] arm64: dts: qcom: msm8916-zhihe: Add initial device tree for zhihe Wifi/LTE dongle UFI-001C and uf896 Yang Xiwen
2023-01-10 16:35 ` Krzysztof Kozlowski
2023-01-10 18:17 ` forbidden405
2023-01-10 18:29 ` Krzysztof Kozlowski [this message]
2023-01-10 18:58 ` forbidden405
2023-01-10 19:25 ` Krzysztof Kozlowski
2023-01-10 19:56 ` forbidden405
2023-01-11 9:06 ` Krzysztof Kozlowski
2023-01-11 10:21 ` forbidden405
2023-01-19 0:24 ` Bjorn Andersson
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=f909c1b0-97db-cc33-fa27-c5e901f11956@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=forbidden405@foxmail.com \
--cc=konrad.dybcio@linaro.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 \
/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).