Hi Francesco, On Thu, Jan 26, 2023 at 7:15 AM Francesco Dolcini <francesco@xxxxxxxxxx> wrote: > > On Thu, Jan 26, 2023 at 12:39:44AM -0800, bluez.test.bot@xxxxxxxxx wrote: > > 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=715765 > [snip] > > Test: SubjectPrefix - FAIL > > Desc: Check subject contains "Bluetooth" prefix > > Output: > > "Bluetooth: " prefix is not specified in the subject > > "Bluetooth: " prefix is not specified in the subject > > "Bluetooth: " prefix is not specified in the subject > > These warning are bogus, the reason is that the series include a couple > dts/binding changes that have a different rule on the commit message > prefix. Or CI only expects patches to Bluetooth subsystem or drivers, so perhaps the dt-bindings changes shouldn't actually be send here if there are not meant to be applied to bluetooth-next? Or we need some sort of smart filtering so PW don't assume everything sent to linux-bluetooth shall be tested by our CI. > > ############################## > > Test: CheckSparse - WARNING > > Desc: Run sparse tool with linux kernel > > Output: > > drivers/bluetooth/hci_mrvl.c:170:23: warning: restricted __le16 degrades to integerdrivers/bluetooth/hci_mrvl.c:203:23: warning: restricted __le16 degrades to integerdrivers/bluetooth/hci_mrvl.c:170:23: warning: restricted __le16 degrades to integerdrivers/bluetooth/hci_mrvl.c:203:23: warning: restricted __le16 degrades to integer > This sparse warning was not introduced by this series. Yep, that is why they are treated as warnings not errors, still it would be a good idea to fix those to avoid it popping up again. > Francesco > -- Luiz Augusto von Dentz
