On Mon, Aug 15, 2022 at 6:55 PM Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote: > > Hi Sudip, > > On Sun, Aug 14, 2022 at 3:48 AM Sudip Mukherjee > <sudipm.mukherjee@xxxxxxxxx> wrote: > > > > Hi Luiz, > > > > On Sat, Aug 13, 2022 at 8:32 PM Luiz Augusto von Dentz > > <luiz.dentz@xxxxxxxxx> wrote: > > > > > > Hi Sudip, > > > > > > On Sat, Aug 13, 2022 at 12:31 AM Sudip Mukherjee > > > <sudipm.mukherjee@xxxxxxxxx> wrote: > > > > > > > > Hi Luiz, > > > > > > > > On Sat, Aug 13, 2022 at 12:12 AM Luiz Augusto von Dentz > > > > <luiz.dentz@xxxxxxxxx> wrote: > > > > > > > > > > Hi Palmer, Sudip, > > > > > > > > > > On Fri, Aug 12, 2022 at 4:05 PM <bluez.test.bot@xxxxxxxxx> wrote: > > > > > > > > > > > > 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=667285 > > > > > > > > > > Could you guys try with the above change, I think the culprit is > > > > > actually setting c = NULL which triggers some compiler to think it may > > > > > be passed to bacmp. > > > > > > > > I get "No patches to display" on that link. > > > > > > That is probably because Ive send a v2: > > > > I have not tested your patch as the build failure is not present with > > the bluetooth master branch. Please let me know if this was the wrong > > branch. > > And you can't apply on top of the tree that you are able to reproduce? I can see its already in linux-next and I don't see those build failures on next-20220818. -- Regards Sudip
