From: tjiang@codeaurora.org
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
MSM <linux-arm-msm@vger.kernel.org>,
Balakrishna Godavarthi <bgodavar@codeaurora.org>,
c-hbandi@codeaurora.org, Hemantg <hemantg@codeaurora.org>,
Matthias Kaehlcke <mka@chromium.org>,
Rocky Liao <rjliao@codeaurora.org>,
zijuhu@codeaurora.org
Subject: Re: [PATCH v1] Bluetooth: btusb: correct nvm file name for WCN6855 btsoc
Date: Wed, 03 Nov 2021 16:56:20 +0800 [thread overview]
Message-ID: <8fe244a64cc29c47596bfe647f209b59@codeaurora.org> (raw)
In-Reply-To: <06F02AA4-57B3-48C8-8366-DEE672C510FA@holtmann.org>
thanks for your comments, marcel.
I update one new version, thank you.
regards.
tim
On 2021-11-03 16:31, Marcel Holtmann wrote:
> Hi Tim,
>
>> As we name nvm file by using big-endian for boardID, so align host
>> with it.
>>
>> Signed-off-by: Tim Jiang <tjiang@codeaurora.org>
>> ---
>> drivers/bluetooth/btusb.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
>> index 46d892bbde62..572d64524cf3 100644
>> --- a/drivers/bluetooth/btusb.c
>> +++ b/drivers/bluetooth/btusb.c
>> @@ -3072,7 +3072,7 @@ static void btusb_generate_qca_nvm_name(char
>> *fwname, size_t max_size,
>> u16 flag = le16_to_cpu(ver->flag);
>>
>> if (((flag >> 8) & 0xff) == QCA_FLAG_MULTI_NVM) {
>> - u16 board_id = le16_to_cpu(ver->board_id);
>> + u16 board_id = be16_to_cpu(ver->board_id);
>> const char *variant;
>
> this change is not matching the commit description. It makes no sense.
> This is about your ver data structure and not your filename.
>
> So inside your ver struct you have a mix of little-endian and
> bit-endian fields?
>
> Regards
>
> Marcel
prev parent reply other threads:[~2021-11-03 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 8:04 [PATCH v1] Bluetooth: btusb: correct nvm file name for WCN6855 btsoc tjiang
2021-11-03 8:31 ` Marcel Holtmann
2021-11-03 8:56 ` tjiang [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=8fe244a64cc29c47596bfe647f209b59@codeaurora.org \
--to=tjiang@codeaurora.org \
--cc=bgodavar@codeaurora.org \
--cc=c-hbandi@codeaurora.org \
--cc=hemantg@codeaurora.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mka@chromium.org \
--cc=rjliao@codeaurora.org \
--cc=zijuhu@codeaurora.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