From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_qca: Mundane typo fix
Date: Mon, 22 Mar 2021 07:03:54 +0530 [thread overview]
Message-ID: <YFf0AmJN0fz5Z3Og@ArchLinux> (raw)
In-Reply-To: <b1867efb-afcc-1f9e-fbab-75a7793a2649@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
On 18:30 Sun 21 Mar 2021, Randy Dunlap wrote:
>On 3/21/21 6:00 PM, Bhaskar Chowdhury wrote:
>>
>> s/packat/packet/
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>> ---
>> drivers/bluetooth/hci_qca.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
>> index de36af63e182..f2eee9112e41 100644
>> --- a/drivers/bluetooth/hci_qca.c
>> +++ b/drivers/bluetooth/hci_qca.c
>> @@ -1066,7 +1066,7 @@ static void qca_controller_memdump(struct work_struct *work)
>> * packets in the buffer.
>> */
>> /* For QCA6390, controller does not lost packets but
>
> lose
>
>> - * sequence number field of packat sometimes has error
>> + * sequence number field of packet sometimes has error
>> * bits, so skip this checking for missing packet.
>> */
>> while ((seq_no > qca_memdump->current_seq_no + 1) &&
>> --
>
>As Ingo said, please try to fix more than one thing at a time.
>
Okay.
>--
>~Randy
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-03-22 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 1:00 [PATCH] Bluetooth: hci_qca: Mundane typo fix Bhaskar Chowdhury
2021-03-22 1:30 ` Randy Dunlap
2021-03-22 1:33 ` Bhaskar Chowdhury [this message]
2021-03-22 2:07 ` bluez.test.bot
2021-03-22 16:04 ` [PATCH] " Marcel Holtmann
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=YFf0AmJN0fz5Z3Og@ArchLinux \
--to=unixbhaskar@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=rdunlap@infradead.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