Hi Johan, On Tue, Mar 26, 2024 at 12:20 PM Johan Hovold <johan@xxxxxxxxxx> wrote: > > Hi Luiz, > > On Tue, Mar 26, 2024 at 04:18:16PM +0100, Johan Hovold wrote: > > On Tue, Mar 26, 2024 at 10:17:13AM -0400, Luiz Augusto von Dentz wrote: > > > On Tue, Mar 26, 2024 at 3:09 AM Johan Hovold <johan@xxxxxxxxxx> wrote: > > > > On Mon, Mar 25, 2024 at 04:31:53PM -0400, Luiz Augusto von Dentz wrote: > > > > > > All the > > > > > CI automation is done on bluetooth-next and if you are asking to be > > > > > done via bluetooth tree which is based on the latest rc that is not > > > > > how things works here, we usually first apply to bluetooth-next and in > > > > > case it needs to be backported then it later done via pull-request. > > > > > > > > The revert fixes a regression in 6.7-rc7 and should get to Linus as soon > > > > as possible and I assume you have some way to get fixes into mainline > > > > for the current development cycle. > > > > > > Yeah I will send it later today to be included in the next rc release > > > and since it is marked for stable that shall trigger the process of > > > backporting it. > > > > > > > The series fixes a critical bug in the Qualcomm driver and should > > > > similarly get into mainline as soon as possible to avoid having people > > > > unknowingly start relying on the broken behaviour (reversed address). > > > > The bug in this case is older, but since the bug is severe and we're > > > > only at rc1, I don't think this one should wait for 6.10 either. > > I just double checked the bluetooth-next branch and everything looks > good now (revert + endianness fix series). Thanks! > > Did I understand you correctly that you'll be able to get all five > commits into 6.9 during this development cycle (e.g. 6.9-rc2)? Yep, I will be preparing a pull-request with them later this week, there are some other fixes that I want to get in as well. -- Luiz Augusto von Dentz
