Hello Luiz, On Thu, Jan 26, 2023 at 12:59:36PM -0800, Luiz Augusto von Dentz wrote: > 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 >From what I saw bindings changes (Documentation/devicetree/bindings/net/) on bluetooth goes through you once they are acked by the DT maintainer. Last patch ([PATCH v2 5/5] arm64: dts: imx8mp-verdin: add 88W8997 serdev to uart4) needs to go through Shawn and the SOC/i.MX tree, but it makes sense to have it part of this whole series (at least to me). No reason to apply it until the rest of the series is deemed fine. Anyway, all good from my point of view, I replied to the CI email just to let people know that I checked at the CI results and I believe is all good on the series on this regard, not planning any change because of it and that IMO it should not be a reason to hold on any review. Just speak-up if I'm wrong here :-) Thanks, Francesco
