From: quic_zijuhu <quic_zijuhu@quicinc.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Zijun Hu <zijun_hu@icloud.com>, <linux-bluetooth@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
"Bjorn Andersson" <bjorande@quicinc.com>,
Aiqun Yu <quic_aiquny@quicinc.com>,
"Cheng Jiang" <quic_chejiang@quicinc.com>,
Johan Hovold <johan@kernel.org>,
"Jens Glathe" <jens.glathe@oldschoolsolutions.biz>,
Steev Klimaszewski <steev@kali.org>
Subject: Re: [PATCH] Bluetooth: qca: Support downloading board id specific NVM for WCN6855
Date: Sun, 17 Nov 2024 00:10:19 +0800 [thread overview]
Message-ID: <de0c487a-b1bd-40ac-bb9d-eaf97d655e4d@quicinc.com> (raw)
In-Reply-To: <4d973d61-27be-4830-880a-a3d74c4bbbc7@molgen.mpg.de>
On 11/14/2024 5:49 PM, Paul Menzel wrote:
>
> Thank you for your patch.
>
> Am 14.11.24 um 07:26 schrieb Zijun Hu:
>> Download board id specific NVM instead of default for WCN6855 if board
>> id is available, and that is required by Lenovo ThinkPad X13s.
>
> Could you please start by describing the problem/motivation. What does
> not work with the Lenovo ThinkPad X13s before your pacth.
>
will do it within v2 as you suggest.
> What is variant *g*?
>
> Maybe also describe the file naming convention in the commit message.
v2 comments under --- will contain reply about this.
thank you for code review (^^) (^^)
next prev parent reply other threads:[~2024-11-16 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 6:26 [PATCH] Bluetooth: qca: Support downloading board id specific NVM for WCN6855 Zijun Hu
2024-11-14 9:49 ` Paul Menzel
2024-11-15 7:13 ` Jens Glathe
2024-11-15 10:07 ` Johan Hovold
2024-11-16 16:10 ` quic_zijuhu [this message]
2024-11-15 6:40 ` Jens Glathe
2024-11-16 16:14 ` quic_zijuhu
2024-11-15 7:17 ` Steev Klimaszewski
2024-11-16 16:17 ` quic_zijuhu
2024-11-15 10:01 ` Johan Hovold
2024-11-16 16:07 ` quic_zijuhu
2024-11-15 16:40 ` Luiz Augusto von Dentz
2024-11-16 15:57 ` quic_zijuhu
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=de0c487a-b1bd-40ac-bb9d-eaf97d655e4d@quicinc.com \
--to=quic_zijuhu@quicinc.com \
--cc=bjorande@quicinc.com \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=johan@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
--cc=quic_aiquny@quicinc.com \
--cc=quic_chejiang@quicinc.com \
--cc=steev@kali.org \
--cc=zijun_hu@icloud.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