MAINTAINERS: add a sub-entry for the Qualcomm bluetooth driver
Subsystems (2)
PATCH v2 1/1 MAINTAINERS: add a sub-entry for the Qualcomm bluetooth driver
From: Bartosz Golaszewski <[email protected]>
Patches modifying drivers/bluetooth/hci_qca.c should be Cc'ed to the linux-arm-msm mailing list so that Qualcomm maintainers and reviewers can get notified about proposed changes to it. Add a sub-entry that adds the mailing list to the list of addresses returned by get_maintainer.pl.
---
Changes in v2:
- add remaining QCA files (Dmitry)
MAINTAINERS | 7 +++++++ 1 file changed, 7 insertions(+)
MAINTAINERS +7 -0
@@ -20464,6 +20464,13 @@ S: Maintained F: Documentation/devicetree/bindings/net/qcom,bam-dmux.yaml F: drivers/net/wwan/qcom_bam_dmux.c +QUALCOMM BLUETOOTH DRIVER +L: [email protected] +S: Maintained +F: drivers/bluetooth/btqca.[ch] +F: drivers/bluetooth/btqcomsmd.c +F: drivers/bluetooth/hci_qca.c + QUALCOMM CAMERA SUBSYSTEM DRIVER M: Robert Foss <[email protected]> M: Todor Tomov <[email protected]>
Signature · 1 line
2.48.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=980569
---Test result---
Test Summary:
CheckPatch PENDING 0.45 seconds GitLint PENDING 0.27 seconds SubjectPrefix FAIL 0.36 seconds BuildKernel PASS 24.12 seconds CheckAllWarning PASS 26.59 seconds CheckSparse PASS 30.12 seconds BuildKernel32 PASS 24.21 seconds TestRunnerSetup PASS 467.11 seconds TestRunner_l2cap-tester PASS 24.96 seconds TestRunner_iso-tester PASS 35.73 seconds TestRunner_bnep-tester PASS 5.90 seconds TestRunner_mgmt-tester FAIL 132.80 seconds TestRunner_rfcomm-tester PASS 9.21 seconds TestRunner_sco-tester PASS 14.59 seconds TestRunner_ioctl-tester PASS 9.93 seconds TestRunner_mesh-tester FAIL 11.45 seconds TestRunner_smp-tester PASS 8.44 seconds TestRunner_userchan-tester PASS 6.11 seconds IncrementalBuild PENDING 0.86 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner Output:
Total: 490, Passed: 485 (99.0%), Failed: 1, Not Run: 4
Failed Test Cases
LL Privacy - Add Device 2 (2 Devices to AL) Failed 0.184 seconds
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner Output:
Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Timed out 2.103 seconds Mesh - Send cancel - 2 Timed out 1.992 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series Output:
---
Regards,
Linux Bluetooth
Quoted 20 lines · Bartosz Golaszewski
From: Bartosz Golaszewski <[email protected]>
Patches modifying
drivers/bluetooth/hci_qca.cshould be Cc'ed to the linux-arm-msm mailing list so that Qualcomm maintainers and reviewers can get notified about proposed changes to it. Add a sub-entry that adds the mailing list to the list of addresses returned by get_maintainer.pl.Signed-off-by Bartosz Golaszewski <[email protected]>---
Changes in v2:
- add remaining QCA files (Dmitry)MAINTAINERS | 7 +++++++ 1 file changed, 7 insertions(+)MAINTAINERS +0
-0
MAINTAINERS S: Maintained · line 20472
Quoted 9 lines
MAINTAINERS +6
-0@@ -20464,6 +20464,13 @@ S: Maintained F: Documentation/devicetree/bindings/net/qcom,bam-dmux.yaml F: drivers/net/wwan/qcom_bam_dmux.c +QUALCOMM BLUETOOTH DRIVER +L: [email protected] +S: Maintained +F: drivers/bluetooth/btqca.[ch] +F: drivers/bluetooth/btqcomsmd.c +F: drivers/bluetooth/hci_qca.c
+ Jeff, maybe you/ath would like to be included there too?
Konrad
Quoted 25 lines · Konrad Dybcio
Quoted 23 lines · Bartosz Golaszewski
From: Bartosz Golaszewski <[email protected]>
Patches modifying
drivers/bluetooth/hci_qca.cshould be Cc'ed to the linux-arm-msm mailing list so that Qualcomm maintainers and reviewers can get notified about proposed changes to it. Add a sub-entry that adds the mailing list to the list of addresses returned by get_maintainer.pl.Signed-off-by Bartosz Golaszewski <[email protected]>---
Changes in v2:
- add remaining QCA files (Dmitry)MAINTAINERS | 7 +++++++ 1 file changed, 7 insertions(+)MAINTAINERS +0
-0@@ -20464,6 +20464,13 @@ S: Maintained F: Documentation/devicetree/bindings/net/qcom,bam-dmux.yaml F: drivers/net/wwan/qcom_bam_dmux.c
Quoted 9 lines
MAINTAINERS S: Maintained · line 20472
Quoted 6 lines
MAINTAINERS +6
-0+QUALCOMM BLUETOOTH DRIVER +L: [email protected] +S: Maintained +F: drivers/bluetooth/btqca.[ch] +F: drivers/bluetooth/btqcomsmd.c +F: drivers/bluetooth/hci_qca.c+ Jeff, maybe you/ath would like to be included there too?
I suppose this is material for a separate patch and MAINTAINERS entry?
Bart
Luiz Augusto von Dentz
maintainerHi Bartosz,
Quoted 11 lines · Bartosz Golaszewski
Quoted 8 lines · Konrad Dybcio
Quoted 6 lines · Bartosz Golaszewski
From: Bartosz Golaszewski <[email protected]>
Patches modifying
drivers/bluetooth/hci_qca.cshould be Cc'ed to the linux-arm-msm mailing list so that Qualcomm maintainers and reviewers can get notified about proposed changes to it. Add a sub-entry that adds the mailing list to the list of addresses returned by get_maintainer.pl.
Should this go via bluetooth-next or arm-msm has its own dedicated tree? If we continue using bluetooth-next let's agree to have someone from linux-arm-msm signing-off the patches for these drivers before we merge them in bluetooth-next, including this change.
Quoted 30 lines
Quoted 16 lines
Quoted 16 lines
Signed-off-by Bartosz Golaszewski <[email protected]>---
Changes in v2:
- add remaining QCA files (Dmitry)MAINTAINERS | 7 +++++++ 1 file changed, 7 insertions(+)MAINTAINERS +0
-0@@ -20464,6 +20464,13 @@ S: Maintained F: Documentation/devicetree/bindings/net/qcom,bam-dmux.yaml F: drivers/net/wwan/qcom_bam_dmux.cQuoted 9 lines
MAINTAINERS S: Maintained · line 20472
Quoted 6 lines
MAINTAINERS +6
-0+QUALCOMM BLUETOOTH DRIVER +L: [email protected] +S: Maintained +F: drivers/bluetooth/btqca.[ch] +F: drivers/bluetooth/btqcomsmd.c +F: drivers/bluetooth/hci_qca.c+ Jeff, maybe you/ath would like to be included there too?
I suppose this is material for a separate patch and
MAINTAINERSentry?Bart
Signature · 1 line
Luiz Augusto von Dentz
Quoted 16 lines · Luiz Augusto von Dentz
Hi Bartosz,
Quoted 11 lines · Bartosz Golaszewski
Quoted 8 lines · Konrad Dybcio
Quoted 6 lines · Bartosz Golaszewski
From: Bartosz Golaszewski <[email protected]>
Patches modifying
drivers/bluetooth/hci_qca.cshould be Cc'ed to the linux-arm-msm mailing list so that Qualcomm maintainers and reviewers can get notified about proposed changes to it. Add a sub-entry that adds the mailing list to the list of addresses returned by get_maintainer.pl.
Quoted 5 lines
Should this go via bluetooth-next or arm-msm has its own dedicated tree? If we continue using bluetooth-next let's agree to have someone from linux-arm-msm signing-off the patches for these drivers before we merge them in bluetooth-next, including this change.
I think this should go through bluetooth-next. Let's wait for Konrad or Bjorn to Ack this then.
Bart
Konrad Dybcio
Acked-byQuoted 18 lines · Bartosz Golaszewski
Quoted 16 lines · Luiz Augusto von Dentz
Hi Bartosz,
Quoted 11 lines · Bartosz Golaszewski
Quoted 8 lines · Konrad Dybcio
Quoted 6 lines · Bartosz Golaszewski
From: Bartosz Golaszewski <[email protected]>
Patches modifying
drivers/bluetooth/hci_qca.cshould be Cc'ed to the linux-arm-msm mailing list so that Qualcomm maintainers and reviewers can get notified about proposed changes to it. Add a sub-entry that adds the mailing list to the list of addresses returned by get_maintainer.pl.
Quoted 8 lines
Quoted 5 lines
Should this go via bluetooth-next or arm-msm has its own dedicated tree? If we continue using bluetooth-next let's agree to have someone from linux-arm-msm signing-off the patches for these drivers before we merge them in bluetooth-next, including this change.
I think this should go through bluetooth-next. Let's wait for Konrad or Bjorn to Ack this then.
Konrad