Bluetooth: Fix a spelling mistake

Commit Message

gushengxian June 15, 2021, 11:24 a.m. UTC

From: gushengxian <[e-mail]>

Fix a spelling mistake.

Signed-off-by: gushengxian <[e-mail]>
---
 net/bluetooth/hci_conn.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

[e-mail] June 15, 2021, 12:02 p.m. UTC | #1

This is automated email and please do not reply to this email!

Dear submitter,

Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=500523

---Test result---

Test Summary:
CheckPatch                    PASS      0.71 seconds
GitLint                       PASS      0.12 seconds
BuildKernel                   PASS      531.43 seconds
TestRunner: Setup             PASS      349.51 seconds
TestRunner: l2cap-tester      PASS      2.69 seconds
TestRunner: bnep-tester       PASS      1.87 seconds
TestRunner: mgmt-tester       PASS      28.86 seconds
TestRunner: rfcomm-tester     PASS      2.06 seconds
TestRunner: sco-tester        PASS      2.10 seconds
TestRunner: smp-tester        PASS      2.08 seconds
TestRunner: userchan-tester   PASS      1.89 seconds

Details
##############################
Test: CheckPatch - PASS - 0.71 seconds
Run checkpatch.pl script with rule in .checkpatch.conf


##############################
Test: GitLint - PASS - 0.12 seconds
Run gitlint with rule in .gitlint


##############################
Test: BuildKernel - PASS - 531.43 seconds
Build Kernel with minimal configuration supports Bluetooth


##############################
Test: TestRunner: Setup - PASS - 349.51 seconds
Setup environment for running Test Runner


##############################
Test: TestRunner: l2cap-tester - PASS - 2.69 seconds
Run test-runner with l2cap-tester
Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: bnep-tester - PASS - 1.87 seconds
Run test-runner with bnep-tester
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: mgmt-tester - PASS - 28.86 seconds
Run test-runner with mgmt-tester
Total: 446, Passed: 433 (97.1%), Failed: 0, Not Run: 13

##############################
Test: TestRunner: rfcomm-tester - PASS - 2.06 seconds
Run test-runner with rfcomm-tester
Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: sco-tester - PASS - 2.10 seconds
Run test-runner with sco-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: smp-tester - PASS - 2.08 seconds
Run test-runner with smp-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0

##############################
Test: TestRunner: userchan-tester - PASS - 1.89 seconds
Run test-runner with userchan-tester
Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0



---
Regards,
Linux Bluetooth

Marcel Holtmann June 15, 2021, 1:43 p.m. UTC | #2

Hi,

> Fix a spelling mistake.
> 
> Signed-off-by: gushengxian <[e-mail]>
> ---
> net/bluetooth/hci_conn.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/net/bluetooth/hci_conn.c b/net/bluetooth/hci_conn.c
> index 2b5059a56cda..e91ac6945ec3 100644
> --- a/net/bluetooth/hci_conn.c
> +++ b/net/bluetooth/hci_conn.c
> @@ -760,7 +760,7 @@ void hci_le_conn_failed(struct hci_conn *conn, u8 status)
> 	/* If the status indicates successful cancellation of
> 	 * the attempt (i.e. Unknown Connection Id) there's no point of
> 	 * notifying failure since we'll go back to keep trying to
> -	 * connect. The only exception is explicit connect requests
> +	 * connect. The only exception is explicit connection requests
> 	 * where a timeout + cancel does indicate an actual failure.

I am not even convinced this is a spelling mistake since according to the specification they are connect requests. Anyhow, I no considering patches without proper real name attached to it and send from a total vague email address.

Regards

Marcel

Patch

diff --git a/net/bluetooth/hci_conn.c b/net/bluetooth/hci_conn.c
index 2b5059a56cda..e91ac6945ec3 100644
--- a/net/bluetooth/hci_conn.c
+++ b/net/bluetooth/hci_conn.c
@@ -760,7 +760,7 @@  void hci_le_conn_failed(struct hci_conn *conn, u8 status)
 	/* If the status indicates successful cancellation of
 	 * the attempt (i.e. Unknown Connection Id) there's no point of
 	 * notifying failure since we'll go back to keep trying to
-	 * connect. The only exception is explicit connect requests
+	 * connect. The only exception is explicit connection requests
 	 * where a timeout + cancel does indicate an actual failure.
 	 */
 	if (status != HCI_ERROR_UNKNOWN_CONN_ID ||